| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\
| | |
| | | |
upgrade to sbt 0.13.11
|
| | |
| | |
| | |
| | | |
yum! delicious dogfood!
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
reverts the "skip docs on first module build" part of
c4fc2fd42457a87fea9e7af94e0ba2f57e533854 since it was resulting in
module docs never being published at all, which then would later
cause release-website-archives to fail. see
https://github.com/scala/scala-dev/issues/89
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
merge/2.11.x-to-2.12.x-20160225
Conflicts:
scripts/jobs/integrate/bootstrap
src/build/maven/scala-actors-pom.xml
test/files/pos/t3420.flags
Conflicts were trivial to resolve.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Which lets us remove the dependency on sbt-partest-interface,
as this has been incorporated into scala-partest itself.
Conflicts:
scripts/jobs/integrate/bootstrap
|
| |
| |
| |
| | |
Fixes scala/scala-dev#88
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A few small improvements I accumulated in while using this script
to bootstrap the removal of trait implementation classes.
- Allow an extra step to build STARR from a prior commit
- Skip Scaladoc in the module builds first round
- Speed up the step that cleans the remote repo by skipping the
numerous "scala-actors-migration" directories.
I've been using this successully as follows:
(ant all.clean; mkdir ivy2-shadow; export STARR_REF=$(git rev-parse :/"Nuke trait implementation"); export WORKSPACE=$PWD; bash -ex ./scripts/jobs/integrate/bootstrap)
|
| |
| |
| |
| |
| | |
Which lets us remove the dependency on sbt-partest-interface,
as this has been incorporated into scala-partest itself.
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
build.sbt
scripts/jobs/integrate/bootstrap
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
# Improve version handling in the sbt build:
The new settings `baseVersion` and `baseVersionSuffix` make it easier
to set version numbers for different kinds of builds in a consistent
way without e.g. having to first get a git SHA outside of sbt.
The new task `generateBuildCharacterPropertiesFile` writes the file
`buildcharacter.properties` to the root dir. The format is compatible
with the same file produced by the ANT build but it only contains a
subset of the properties, in particular the Maven version, which is
needed in publishing scripts and passed around between different
Jenkins jobs as `jenkins.properties`.
SHAs in version numbers are consistently shortened to 7 digits (as used
by git and github). Previously we used 7 digits in Maven snapshot
version numbers but 10 digits in canonical and OSGi version numbers.
# Add Jenkins script support to the sbt build:
The new command `setupPublishCore` takes the PR validation snapshot
repository as an argument and changes the required settings for the
`publish-core` build (use SHA-SNAPSHOT versioning, compile with
optimization enabled, do not publish scaladoc sets)
For example, the following command can be used to generate
`buildcharacter.properties` with the version numbers needed for PR
validation builds:
sbt setupPublishCore dummy generateBuildCharacterPropertiesFile
The sbt build will now automatically detect and use a “~/.credentials”
file with the credentials for publishing to a remote repository.
# Call sbt from `publish-core`:
The correct`$SBT_CMD` is set directly in `bootstrap` and used by
`publish-core` to first generate `buildcharacter.properties` and then
build and publish. Parsing the git revision, computing a version
number and getting binary dependencies are no longer required in the
script. This is all done in the sbt build.
|
|\| |
|
| | |
|
| |
| |
| |
| | |
experimental for now. destined to be automated via scala-jenkins-infra
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
only trivial merge conflicts here.
not dealing with PR #4333 in this merge because there is a substantial
conflict there -- so that's why I stopped at
63daba33ae99471175e9d7b20792324615f5999b for now
|
| |
| |
| |
| |
| |
| |
| | |
scala-xml 1.0.5 has the fix we need in order to run the scala-xml
tests normally during bootstrapping.
reverts 83554a3c0fb2b57efa293efcc81a947b98a19469
|
| |
| |
| |
| |
| |
| | |
Under 2.12 source level, `scala.xml.XMLTest.escape` fails (see #4451)
https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-bootstrap/60/artifact/logs/builds/*view*/
|
| |
| |
| |
| |
| |
| |
| | |
No change in build.sbt, there's no optimizer settings there yet.
Ignore the inliner warning in presentation/t7678 and run/t8029.scala,
noted in https://issues.scala-lang.org/browse/SI-9378
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
Switch to https while we're at it,
and remove duplicate entry for sbt-plugin-releases
(NOTE: 'organization' <-> 'organisation',
see http://ant.apache.org/ivy/history/latest-milestone/concept.html#patterns)
|
| |
| |
| |
| | |
Backport of 48328cc2a2ae26cf6d6cec5da30605b1be6f0990
|
| |
| |
| |
| | |
Backport of 1a292c3d0fe10699837a02ffd8adc3ea4d3a6d22
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Scalacheck 1.12.x cross-compiles to JS and will take more work to
integrate.
Make sure we never attempt to publish scalacheck to sonatype.
Force checkout module refs in case of dirty workspace.
Backport of f238586d1b9d93533ee9507b56a26a97c2b2501c
|
| |
| |
| |
| | |
Backport of 9cd3e6505aa4285750e63263e2551ab71f36ff8d
|
| |
| |
| |
| | |
Backport of 7b54922b77fe1cf40177fc4a5ee9707bb5d854d2
|
| |
| |
| |
| | |
Backport of 3b2abdf6af87debdfb01f22f185d2a35852218fc
|
|\| |
|
| |
| |
| |
| | |
Companion to https://github.com/scala-ide/uber-build/pull/73
|
| |
| |
| |
| |
| |
| | |
Use 2.12.0-M1 as starr.
Also fixes comment in the bootstrap script.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Scalacheck 1.12.x cross-compiles to JS and will take more work to
integrate.
Make sure we never attempt to publish scalacheck to sonatype.
Force checkout module refs in case of dirty workspace.
|
| |
| |
| |
| | |
The 2.12 distribution will no longer ship an akka-actors jar.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since we're moving to bintray, first centralizing the config of
the repositories we use while bootstrapping a release.
This should not be hardcoded in scala/scala anyway, it's an
implementation detail of our infrastructure, which is defined by
scala/scala-jenkins-infra.
|
|\ \
| | |
| | | |
release script for 2.12.0-M0
|
| | | |
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| |
| |
| |
| |
| | |
so that scala-dist depends on the correctly
cross-versioned scala-continuations-plugin.
|
| |
| |
| |
| | |
... until https://github.com/scala-ide/uber-build/issues/48 is fixed.
|
|/ |
|
| |
|
| |
|
| |
|