summaryrefslogtreecommitdiff
path: root/versions.properties
diff options
context:
space:
mode:
Diffstat (limited to 'versions.properties')
-rw-r--r--versions.properties63
1 files changed, 23 insertions, 40 deletions
diff --git a/versions.properties b/versions.properties
index 4318bfa6e3..5b58ebeaa4 100644
--- a/versions.properties
+++ b/versions.properties
@@ -1,44 +1,27 @@
-#Wed, 23 Jul 2014 08:37:26 +0200
-# NOTE: this file determines the content of the scala-distribution
-# via scala-dist-pom.xml and scala-library-all-pom.xml
-# when adding new properties that influence a release,
-# also add them to the update.versions mechanism in build.xml,
-# which is used by the release script scripts/jobs/integrate/bootstrap
+# Scala version used for bootstrapping (see README.md)
+starr.version=2.12.1
-# The scala version used for bootstrapping. This has no impact on the final classfiles:
-# there are two stages (locker and quick), so compiler and library are always built
-# with themselves. Stability is ensured by building a third stage (strap).
-starr.version=2.11.10
+# The scala.binary.version determines how modules are resolved. It is set as follows:
+# - After 2.x.0 is released, the binary version is 2.x
+# - If the starr is a milestone or RC, the full starr version, e.g., 2.12.0-M2
+#
+# For local development during pre-releases, we use existing module binaries with the hope
+# that binary compatibility does not break. For example, after releasing 2.12.0-M1, we continue
+# using scala-partest_2.12.0-M1 until releasing M2. Manual intervention is necessary for changes
+# that break binary compatibility, see for example PR #5003.
+scala.binary.version=2.12
# These are the versions of the modules that go with this release.
-# These properties are used during PR validation and in dbuild builds.
-
-# The scala.binary.version determines how modules are resolved. For example, it
-# determines which partest artifact is being used for running the tests.
-# It has to be set in the following way:
-# - After 2.x.0 is released, the binary version is 2.x.
-# - During milestones and RCs, modules are cross-built against the full version.
-# So the value is the full version (e.g. 2.12.0-M1).
-scala.binary.version=2.11
-# e.g. 2.11.0-RC1, 2.11.0, 2.11.1-RC1, 2.11.1
-# this defines the dependency on scala-continuations-plugin in scala-dist's pom
-scala.full.version=2.11.10
-
-# external modules shipped with distribution, as specified by scala-library-all's pom
-scala-xml.version.number=1.0.5
-scala-parser-combinators.version.number=1.0.4
-scala-continuations-plugin.version.number=1.0.2
-scala-continuations-library.version.number=1.0.2
-scala-swing.version.number=1.0.2
-akka-actor.version.number=2.3.16
-actors-migration.version.number=1.1.0
+# Artifact dependencies:
+# - scala-compiler: scala-xml, jline (% "optional")
+# - scala-library-all: scala-xml, scala-parser-combinators, scala-swing
+# Other usages:
+# - scala-asm: jar content included in scala-compiler
+# - jline: shaded with JarJar and included in scala-compiler
+# - partest: used for running the tests
+scala-xml.version.number=1.0.6
+scala-parser-combinators.version.number=1.0.5
+scala-swing.version.number=2.0.0
+partest.version.number=1.1.0
+scala-asm.version=5.1.0-scala-2
jline.version=2.14.3
-scala-asm.version=5.0.4-scala-3
-
-# external modules, used internally (not shipped)
-partest.version.number=1.0.16
-scalacheck.version.number=1.11.6
-
-# TODO: modularize the compiler
-#scala-compiler-doc.version.number=1.0.0-RC1
-#scala-compiler-interactive.version.number=1.0.0-RC1