summaryrefslogtreecommitdiff
path: root/lib/scala-library.jar.desired.sha1
diff options
context:
space:
mode:
authorAdriaan Moors <adriaan.moors@typesafe.com>2013-07-16 10:55:29 -0700
committerAdriaan Moors <adriaan.moors@typesafe.com>2013-07-16 11:00:02 -0700
commit37dc3e4e41fdf0cc2c0da7936918dc90278e3346 (patch)
tree624718f9ac65668992f0e93df9823461cb1b2645 /lib/scala-library.jar.desired.sha1
parent64619ce5b22372330119613712b0f5b209e8d245 (diff)
downloadscala-37dc3e4e41fdf0cc2c0da7936918dc90278e3346.tar.gz
scala-37dc3e4e41fdf0cc2c0da7936918dc90278e3346.tar.bz2
scala-37dc3e4e41fdf0cc2c0da7936918dc90278e3346.zip
STARR: use 2.11.0-M4, built with 2.11.0-M3
Replaced starr jars with 2.11.0-M4, built with Scala 2.11.0-M3. I used `ant replacestarr-opt -Dstarr.use.released=1`, with `starr.number`: ``` starr.version=2.11.0-M3 ``` Then pushed the jars to artifactory after moving `lib/jline.jar` out of the way, as it's no longer "desired" (i.e., not pulled from artifactory). Its presence seemed to break `./push-binary-libs.sh $ARTIFACTORY_USER $ARTIFACTORY_PASS`. You can by-pass the custom starr artifact download and use a (released) version of Scala by changing your `build.properties` to include ``` starr.use.released=1 ``` You may optionally change `starr.version` in `starr.number` to whichever version that maven can resolve for you.
Diffstat (limited to 'lib/scala-library.jar.desired.sha1')
-rw-r--r--lib/scala-library.jar.desired.sha12
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/scala-library.jar.desired.sha1 b/lib/scala-library.jar.desired.sha1
index 36aedb2ad7..b7befab52a 100644
--- a/lib/scala-library.jar.desired.sha1
+++ b/lib/scala-library.jar.desired.sha1
@@ -1 +1 @@
-36456c52b0395fc1e6e367291e45bd503fa019c5 ?scala-library.jar
+12007d1b1b913b563093b22e947e6c05fe40f3de ?scala-library.jar