diff options
| author | Adriaan Moors <adriaan.moors@typesafe.com> | 2013-07-16 10:55:29 -0700 |
|---|---|---|
| committer | Adriaan Moors <adriaan.moors@typesafe.com> | 2013-07-16 11:00:02 -0700 |
| commit | 37dc3e4e41fdf0cc2c0da7936918dc90278e3346 (patch) | |
| tree | 624718f9ac65668992f0e93df9823461cb1b2645 /src | |
| parent | 64619ce5b22372330119613712b0f5b209e8d245 (diff) | |
| download | scala-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 'src')
0 files changed, 0 insertions, 0 deletions