scala - The Scala programming language

	Commit message (Collapse)	Author	Age	Files	Lines
*	STARR: use 2.11.0-M4, built with 2.11.0-M3	Adriaan Moors	2013-07-16	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Merge 2.10.x into master	Adriaan Moors	2013-04-02	1	-1/+1
\| \| \| \| \|	Conflicts: build.xml
*	Preparation for faster PR validation	Adriaan Moors	2013-03-26	1	-0/+1
	Added starr.number, so that `ant -propertyfile starr.number -Dlocker.skip=1` works across branches. Introduced target `test.core`, which skips `test.stability`, since that requires `locker == quick`, whereas `locker == starr` with the above settings. (It's interesting to see for which files it fails when that assumption is broken.) Stability will still be tested on a nightly basis. It's rarely broken.