summaryrefslogtreecommitdiff
path: root/versions.properties
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Revert "SI-7624 Fix -feature warnings in scala/tools/scalap"Grzegorz Kossakowski2014-02-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit f2de2c4ec43180351ef1f306bcc5f24643ba5477 because it broke both lift-json and json4s libraries that depend on scalap's APIs. Arguably, those libraries shouldn't depend on unofficial APIs but they do because they had no better alternative at the time (no Scala reflection). The cost of breaking them is not worth minor change of the package. The f2de2c4ec43180351ef1f306bcc5f24643ba5477 mixed two things: 1. Fixing feature warnings 2. Changing package name When reverting (and resolving conflicts) I tried to keep 1. and revert just 2. However, there were also some questionable changes related to 1. that got reverted. In particular, a package object with implicit members that enable language features is an anti-pattern because members of package object are visible both _within_ and _outside_ of the package. Therefore, user could use wildcard import for importing everything from scalap package and enabled postfixOps language feature unknowingly. I went for just adding imports in just those few files where they were needed. Amended by Adriaan: To allow faster turn around, I re-enabled resolving partest from sonatype, as its version needs to be bumped and I don't want to wait for maven central synch. Conflicts: src/partest/scala/tools/partest/nest/Runner.scala src/scalap/scala/tools/scalap/scalax/rules/Memoisable.scala src/scalap/scala/tools/scalap/scalax/rules/Rule.scala src/scalap/scala/tools/scalap/scalax/rules/Rules.scala src/scalap/scala/tools/scalap/scalax/rules/scalasig/ClassFileParser.scala src/scalap/scala/tools/scalap/scalax/rules/scalasig/ScalaSig.scala
* Versions of modules part of Scala 2.11.0-M8.Adriaan Moors2014-01-231-5/+6
|
* scala-library-all: dependency for those who want it allAdriaan Moors2013-12-191-0/+4
| | | | | | | If you'd rather depend on all Scala has to offer, module-wise, depend on scala-library-all. This dependency determines the jars that ship with the Scala distribution. To achieve parity via maven resolution, this is the artifact to depend on.
* Modularize the swing library.Adriaan Moors2013-12-131-0/+1
| | | | | The Scala Swing library will still ship with 2.11 (albeit unsupported). It now resides at https://github.com/scala/scala-swing.
* Modularize continuations plugin.Adriaan Moors2013-12-131-1/+7
| | | | | The continuations plugin and library will still ship with 2.11 (albeit unsupported). They now reside at https://github.com/scala/scala-continuations.
* 2.11.0-M7 starr, 1.11.1 scalacheck, bump modules.Adriaan Moors2013-11-201-6/+6
| | | | | Also consult `extra-repo` more liberally to make it easier to test e.g., a staged scalacheck while releasing modules.
* Refactoring to prepare modularization of the compiler.Adriaan Moors2013-11-121-2/+7
| | | | | | | | | | | | | | | | | | Actual modularization is delayed until 2.12. The one big (one-line) change is to make the interactive compiler independent of scaladoc. We have one "integration test": `MemoryLeaksTest`. This commit adds a bunch of comments marked `TODO: modularize the compiler`, that should be uncommented when we're ready to continue the modularization effort. I decided to merge them commented out to avoid having to rebase xml patches. There's still some chance of bitrot, but I'm willing to take my chances. I previously refactored the build to make it easier to add jars in a coherent way, which hinges on the `init-project-prop` mechanism, so the relevant properties are already injected there.
* M6 modules, partest depends on scala as provided.Adriaan Moors2013-11-111-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new partest now marks its scala dependencies as provided. This is much more robust than before, and it breaks ugly cycles. Updated the build for partest-extras to provide the required scala-compiler dependency. Also, upgrade pax-url-aether to 1.6.0. Since our jenkins uses mirrors with passwords, we needed a fix for https://ops4j1.jira.com/browse/PAXURL-217 in order to run osgi.test on jenkins, now that we use maven more. We didn't hit this bug before because we were using a standard location for the maven local repository, but that causes problems with concurrent jenkins jobs accessing it. So, I added the following to `~/.m2/settings`, and then ran into the issue described above. Also removed some non-essential uses of the extra-repo (slows stuff down), and added a comment of how to make the osgi tests look in a certain local m2 repo (for /some/ operations...) ``` <!-- Maven repos are not safe for concurrent access, thus give each job its own. The WORKSPACE env var is set by jenkins to the path of the current job's workspace. This settings file will cause ant/maven to break if WORKSPACE is not set (to a writeable directory). I don't know how to encode a fall back, but I assume it's not needed as this is ~jenkins/.m2/settings.xml --> <localRepository>${WORKSPACE}/m2repo</localRepository> ```
* Upgrade: starr=M5, partest=RC5, xml=RC4, parsers=RC2.Adriaan Moors2013-09-191-5/+5
|
* Remove scala-xml and scala-parser-combinatorsAdriaan Moors2013-08-271-1/+1
| | | | | | | | | | | | | | | | | | | These modules move to their own repositories: - https://github.com/scala/scala-xml (v1.0-RC3) - https://github.com/scala/scala-parser-combinators (v1.0-RC1) The modularization depends on the new partest, as the old one's classpath handling did not support a modularized scala. The compiler pom now depends on the artifacts published separately, with versions specified in versions.properties. NOTES: - The osgi tests resolve the xml and parsers jars and osgi-fy them, as they are no longer built locally. TODO: Can we move the osgification to the module builds? - Disabled local repositories: don't want to accidentally include unpublished artifacts in releases etc.
* Use scala-partest 1.0-RC4Adriaan Moors2013-08-211-1/+1
| | | | | | | | | | RC3 had a binary incompatibility that led to a crash in parsing options, due to: - https://github.com/scala/scala-partest/commit/9ff138ab4b - https://github.com/scala/scala/commit/2b1563fa74 Also added sonatype as a repo for resolving partest, so we don't have to wait for artifacts to synch to maven central.
* Move partest to https://github.com/scala/scala-partestAdriaan Moors2013-08-201-0/+7
As partest is now resolved from maven, `test/partest` uses `ant test.suite.init` to determine the classpath (serialized to build/pack/partest.properties) that's necessary to run `scala.tools.partest.nest.ConsoleRunner`. Thus, partest gets exactly the same classpath, whether run from the command line through `test/partest` or via `ant test`. The version of partest we're using is specified by properties defined in versions.properties (formerly `starr.number`). Currently, we're using: ``` scala.binary.version=2.11.0-M4 partest.version.number=1.0-RC3 ``` NOTES: - The version of Scala being tested must be backwards binary compatible with the version of Scala that was used to compile partest. - Once 2.11 goes final, `scala.binary.version=2.11`, and `starr.version=2.11.0`. - Need scalacheck on classpath for test/partest scalacheck tests. - Removed atrophied ant tests (haven't been run/changed for at least two years I checked 81d659141a as a "random" sample). - Removed scalacheck. It's resolved as a partest dependency. - For now, use a locally built scalap - Kept the trace macro in the main repo (partest-extras) - New targets for faster pr validation: test-core-opt, test-stab-opt - Reused partest eclipse/intellij project to partest-extras (note: the partest dependency is hard-coded)
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-28 18:13:09 +0000