summaryrefslogtreecommitdiff
path: root/versions.properties
Commit message (Collapse)AuthorAgeFilesLines
* Bump versions on 2.11.9 releaseAdriaan Moors2017-03-281-2/+2
|
* SI-9762 Update to JLine 2.14.3Jason Zaugg2017-01-091-1/+1
| | | | | | | | | | | | | | | | | | Cherry-picked 365ac03 (and bumped from 2.14.1 to 2.14.3) Motivated by the improvements to multi-byte character handling. Screencast showing the reported bug is fixed: http://g.recordit.co/ie1Z367NUl.gif Here's the changelog since JLine 2.12.1: https://github.com/jline/jline2/compare/jline-2.12.1...jline-2.14.3 I needed to disable a new, on-by-default feature in JLine so that it didn't add a " " after completing the token `equals` in `foo.equa<TAB>`.
* Restarr on 2.11.8-18269eaAdriaan Moors2017-01-051-1/+1
|
* move to latest Akka 2.3.x releaseSeth Tisue2016-10-311-1/+1
| | | | | Akka 2.3.16 was released in October 2016: http://akka.io/news/2016/10/30/akka-2.3.16-released.html
* Use sbt for PR validationStefan Zeiger2016-06-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Support directories in `-doc-external-doc`: It is documented as accepting a “classpath_entry_path” for the keys but this only worked for JARs and not for individual class files. When checking for external-doc mappings for a Symbol, we now find the root directory relative to a class file instead of using the full class file path. The corresponding tests for SI-191 and SI8557 are also fixed to support individual class files instead of JARs in partest. This is required for the sbt build which runs partest on “quick” instead of “pack”. - Fix version and repository handling for bootstrapping. The bootstrap `scalaInstance` can now be resolved from any repository added to the project (not just the bootstrap repositories) by using a different workaround for https://github.com/sbt/sbt/issues/1872. - Workaround for https://github.com/sbt/sbt/issues/2640 (putting the wrong `scalaInstance` on partest’s classpath). The required `ScalaInstance` constructor is deprecated, so we have to disable deprecation warnings and fatal warnings until there is a better fix. - Add MiMa to the sbt build (port of the old `test.bc` ant task). The sbt-mima plugin doesn’t have all the features we need, so we do it manually in a similar way to what the plugin does. Checks are done in both directions for the `library` and `compiler` projects. The base version has to be set in `build.sbt`. When set to `None`, MiMa checks are skipped. MiMa checks are run sequentially to avoid spurious errors (see https://github.com/typesafehub/migration-manager/issues/115). - Port the OSGi tests to the sbt build. The set of JARs that gets copied into build/osgi as bundles is a bit different from the ant build. We omit the source JARs but add additional modules that are part of the Scala distribution, which seems more correct. - Get rid up `pull-binary-libs.sh` for the sbt build. Add artifacts are resolved from the special bootstrap repository through Ivy. The special `code.jar` and `instrumented.jar` artifacts are copied to the location where partest expects them (because these paths are hardcoded in partest). Other extra JARs for partest in `test/files/lib` are referenced directly from the Ivy cache. - Move common settings that should be available with unqualified names in local `.sbt` files and on the command line into an auto-plugin. - Add an `antStyle` setting to sbt to allow users to easily enable ant-style incremental compilation instead of sbt’s standard name hashing with `set antStyle := true`. - Disable verbose `info`-level logging during sbt startup for both, `validate/test` and `validate/publish-core` jobs. Update logging is no longer disabled when running locally (where it is useful and doesn’t generate excessive output). - Pass optimization flags for scalac down to partest, using the new partest version 1.0.15\6. - Call the new sbt-based PR validation from `scripts/jobs/validate/test`. - Disable the tests `run/t7843-jsr223-service` and `run/t7933` from https://github.com/scala/scala/pull/4959 for now. We need to set up a new test project (either partest or junit) that can run them on a packaged version of Scala, or possibly move them into a separate project that would naturally run from a packaged Scala as part of the community build.
* Merge pull request #5026 from SethTisue/scala-xml-version-bumpLukas Rytz2016-03-221-1/+1
|\ | | | | upgrade to latest scala-xml (namely 1.0.5)
| * Merge branch '2.11.x' into scala-xml-version-bumpSeth Tisue2016-03-091-2/+2
| |\
| * | upgrade to latest scala-xml (namely 1.0.5)Seth Tisue2016-03-081-1/+1
| | | | | | | | | | | | | | | there shouldn't be user-visible changes since 1.0.4, but regardless, it's good to depend on the latest
* | | Merge branch '2.11.x' into newer-akkaSeth Tisue2016-03-091-2/+2
|\ \ \ | | |/ | |/|
| * | bump versions after 2.11.8 releaseSeth Tisue2016-03-081-2/+2
| |/
* / bundle a newer Akka actors jarSeth Tisue2016-03-091-1/+1
|/ | | | | | | | | | might as well let people have the current stuff. I asked the Akka folks and nobody saw a reason not to upgrade. this version of Akka is the latest in the 2.3.x series, but is also some months old, so no stability worries. (this would have been included in 2.11.8 if I had thought of it in time)
* Update to partest 1.0.13Jason Zaugg2016-02-171-1/+1
| | | | | | | | Which lets us remove the dependency on sbt-partest-interface, as this has been incorporated into scala-partest itself. Conflicts: scripts/jobs/integrate/bootstrap
* Update partest to 1.0.12, test case for reporting invalid flagsLukas Rytz2016-02-171-1/+1
| | | | | | Conflicts: test/files/pos/t3420.flags versions.properties
* Make all of partest work in the sbt buildStefan Zeiger2015-12-041-1/+1
| | | | | | | | | | | | - Fix the scoping of files/lib/*.jar. These files were not on the classpath when running partest from sbt. - Pass the same standard Java options to partest as from the command line. This requires new versions of scala-partest and scala-partest-interface. - Fix the classpath scanning in jvm/innerClassEnclMethodJavaReflection. It only worked for JARs and relative directories but not for absolute directory paths (which are produced by sbt).
* use latest partest (1.0.9)Seth Tisue2015-09-181-1/+1
| | | | | | | | | | | | the new version should be no different, from this repo's perspective, since the changes made between 1.0.7 and 1.0.9 had only to do with build and packaging. nonetheless, we should be using the latest latest to help guard against regressions. (my other motive is that I'm contemplating fixing a partest issue that would result in a 1.0.10 release, so I'd like to have the upgrade to 1.0.9 in place first, so if anything goes wrong there is less searching to do for the cause)
* Fix typos in spec, docs and commentsMichał Pociecha2015-08-231-1/+1
|
* Upgrade scala-asm to 5.0.4-scala-3Lukas Rytz2015-07-281-1/+1
| | | | | Fixes a crash in the backend when the bytecode of a method is too large (https://github.com/scala/scala-asm/issues/8).
* Bump versions after 2.11.7 releaseSeth Tisue2015-06-241-2/+2
|
* Producers / Consumers AnalysisLukas Rytz2015-06-221-1/+1
| | | | | | | | | | | | | | ASM has a built-in `SourceValue` analysis which computes for each value a set of instructions that may possibly have constructed it. The ProdConsAnalyzer class provides additional queries over the result of the SourceValue analysis: - consumers of values - tracking producers / consumers through copying operations (load, store, etc) A fix to (and therefore a new version of) ASM was required. See here: https://github.com/scala/scala-asm/commit/94106a5472
* Nullness AnalysisLukas Rytz2015-05-221-1/+1
| | | | | | | | Tracks nullness of values using an ASM analyzer. Tracking nullness requires alias tracking for local variables and stack values. For example, after an instance call, local variables that point to the same object as the receiver are treated not-null.
* Merge pull request #4499 from lrytz/removeAsmLukas Rytz2015-05-121-0/+1
|\ | | | | Move ASM out of the repository [ci: last-only]
| * Include ASM as a dependency in ANT buildLukas Rytz2015-05-111-0/+1
| | | | | | | | The classfiles are still integrated into scala-compiler.jar.
* | [backport] Revert back to Scalacheck 1.11.x, fixes to bootstrap scriptAdriaan Moors2015-05-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | 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] Update versions.properitesLukas Rytz2015-05-061-9/+12
| | | | | | | | | | | | | | | | | | | | The tagged revisions of the modules integrate the latest release of the sbt-scala-modules sbt plugin. This enables building with a new scala binary version (e.g. 2.12.0-M1) without failinig MiMa. Also updates the other external dependencies. Backport of 8da073cd6bfaaaf3789fc8b70a61ebb66a2f0ded
* | [backport] Comments in versions.propertiesLukas Rytz2015-05-061-2/+8
| | | | | | | | Backport of f9153619380d755a531f887fe0bd63b6e6a91738
* | [backport] Remove starr.use.released property (not in use anymore)Lukas Rytz2015-05-061-1/+0
|/ | | | Backport of 3b2abdf6af87debdfb01f22f185d2a35852218fc
* Bump partest to 1.0.6Adriaan Moors2015-03-311-1/+1
| | | | To enable #4285
* Bump versions after 2.11.6 release.Adriaan Moors2015-03-021-2/+2
|
* Merge pull request #4296 from lrytz/t9105Adriaan Moors2015-02-131-1/+1
|\ | | | | Fixes and tests for InnerClass / EnclsoingMethod classfile attributes
| * Test java reflection on scala library / reflect / compiler jarsLukas Rytz2015-02-071-1/+1
| | | | | | | | | | | | | | Run a number of Java reflection operations on all classes in scala library / reflect / compiler. The test is based on a draft by Jason.
* | SI-8759 bump jline: support alt-gr-based keyboardsAdriaan Moors2015-02-121-1/+1
|/ | | | | | | Users of German & Swedish keyboards can again type `]` in the REPL without crazy acrobatics. Fixed upstream in https://github.com/jline/jline2/pull/175
* Merge pull request #4213 from soc/topic/scala-partest-1.0.3Adriaan Moors2015-02-051-1/+1
|\ | | | | Update scala-partest dependency to 1.0.3
| * Update scala-partest dependency to 1.0.3Simon Ochsenreither2014-12-161-1/+1
| |
* | Bump versions for 2.11.5 release.Adriaan Moors2015-01-041-2/+2
| |
* | update to scala-parser-combinators 1.0.3Antoine Gourlay2014-12-151-1/+1
|/
* Upgrade to scala-xml v1.0.3Adriaan Moors2014-12-041-1/+1
| | | | ... to avoid having to revert the fix for SI-8253
* Fix InnerClass / EnclosingMethod attributesLukas Rytz2014-09-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit seems bigger than it is. Most of it is tests, and moving some code around. The actual changes are small, but a bit subtle. The InnerClass and EnclosingMethod attributes should now be close to the JVM spec (which is summarized in BTypes.scala). New tests make sure that changes to these attributes, and changes to the way Java reflection sees Scala classfiles, don't go unnoticed. A new file, BCodeAsmCommon, holds code that's shared between the two backend (it could hold more, future work). In general, the difficulty with emitting InnerClass / EnclosingMethod is that we need to find out source-level properties. We need to make sure to do enough phase-travelling, and work around destructive changes to the ownerchain in lambdalift (we use originalOwner a lot). The change to JavaMirrors is prompted by the change to the EnclosingMethod attribute, which changes Java reflection's answer to getEnclosingMethod and getEnclosingConstructor. Classes defined in field initializers no longer have an enclosing method, just an enclosing class, which broke an assumption in JavaMirrors. There's one change in erasure. Before this change, when an object declaration implements / overrides a method, and a bridge is required, then the bridge method was actually a ModuleSymbol (it would get the lateMETHOD flag and be emitted as a method anyway). This is confusing, when iterating through the members of a class, you can find two modules with the same name, and one of them doesn't have a module class. Now, such bridge methods will be MethodSymbols. Removed Symbol.originalEnclosingMethod, that is a backend thing and doesn't need to live in the symbol API.
* Bump versions for Scala 2.11.2Lukas Rytz2014-07-231-6/+6
|
* Bump jline version to 2.12 (Re: SI-8535)Adriaan Moors2014-07-151-0/+1
| | | | Move version info where it belongs: versions.properties
* Bump versions for Scala 2.11.1Adriaan Moors2014-05-201-6/+6
|
* Bump akka-actor version to 2.3.3 (ref SI-8549)Adriaan Moors2014-05-191-1/+1
| | | | | Because serialization affected akka, we're upgrading the included akka-actor to 2.3.3, which is built with Scala 2.11.1.
* Bump versions after release of 2.11.0-finalJason Zaugg2014-04-161-4/+4
| | | | | | New versions.properties generated by: https://scala-webapps.epfl.ch/jenkins/view/scala-release-2.11.x/job/scala-release-2.11.x/57/
* Bump Akka version to 2.3.2Jason Zaugg2014-04-151-1/+1
| | | | | | | | | | | | Quoth @rkuhn: > seeing that you are cutting a Scala release, we’ll need to > decide on which Akka version to bundle with it. 2.3.0 has > some remoting bugs which we’d like to leave behind Given the difficult of overriding the bundled Akka version from the Scala script runner (SI-8472), we've deemed it worthwhile to bump the Akka version before releasing 2.11.0.
* Bump versions after release of Scala 2.11.0-RC4Jason Zaugg2014-04-151-4/+4
| | | | | | | | | | Based on: https://scala-webapps.epfl.ch/jenkins/view/scala-release-2.11.x/job/scala-release-2.11.x/52/artifact/scala/versions.properties With a manual edit of the new property, scala.full.version, which was not written out by `ant -Dupdate.versions`. That has since been remedied.
* Render scala.full.version to versions.properties.Adriaan Moors2014-04-041-3/+7
| | | | | | | | | | | | | | | When called with -Dupdate.versions, the build will render its current set of versions to versions properties. This is used during releases, when bootstrapping to a consistent set of modules that constitute a release. Particularly, scala.full.version is the non-SNAPSHOT full version of scala that's closed to maven.version.number. It's similar in spirit to the module build's snapshotScalaBinaryVersion, except that it's always the full version, so, e.g., 2.11.1 rather than 2.11. This version is so far only used to determine the dependency on scala-continuations-plugin in scala-dist.
* Further tweak version of continuations plugin in scala-dist.pomJason Zaugg2014-04-031-0/+4
| | | | | | | | | | | | | | | | | | | | While we must use full version, rather than the cross version (12720e699), we need to use latest non-snapshot version. This should avoid failures like: https://jenkins.scala-ide.org:8496/jenkins/view/Scala%20Xsource%20flag%20nightlies/job/Akka/63/console Such as: [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: UNRESOLVED DEPENDENCIES :: [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: org.scala-lang.plugins#scala-continuations-plugin_2.11.0-SNAPSHOT;1.0.1: not found [warn] :::::::::::::::::::::::::::::::::::::::::::::: sbt.ResolveException: unresolved dependency: org.scala-lang.plugins#scala-continuations-plugin_2.11.0-SNAPSHOT;1.0.1:
* Bump versions for 2.11.0-RC3Adriaan Moors2014-03-181-8/+8
|
* RC3 will ship with akka-actor 2.3.0v2.11.0-RC3Adriaan Moors2014-03-181-1/+1
|
* Bump versions for 2.11.0-RC1Adriaan Moors2014-02-271-10/+10
|
* Bump akka-actor version to 2.3.0-RC4Adriaan Moors2014-02-271-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-09 19:32:56 +0000