mirror of
https://github.com/sbt/sbt.git
synced 2026-09-07 02:55:23 +02:00
Mark Harrah
e83038bed4
The reported issue was a JLine class not being found on sbt startup. JLine was depended on in the sbt build in two places, one with an extra attribute (component) and one without. The retrieve pattern used by the launcher includes that extra attribute. Previously, the dependency without the attribute was selected and jline properly ended up on the sbt classpath. Now, either by bumping JLine to 2.11 or some other insignificant change, jline ends up in a subdirectory for the component and doesn't get on the classpath. (The move in 0.10 away from retrieving based on patterns and using things directly from the cache was good, but this can't be used in the launcher until a hash-based artifact is used so that sbt+Scala jars aren't deleted or overwritten while sbt runs.) A secondary issue was that the compiler-interface-src artifact didn't have a configuration and was therefore not included in the published artifacts.
sbt 0.13
This is the 0.13.x series of sbt.
- Setup: Describes getting started with the latest binary release.
- See CONTRIBUTING for how to build from source, open an issue, fix or add documentation, or submit a pull request.
- FAQ: Explains how to get help, how to migrate from 0.7.7, and more.
- There is a video of a demo given at Scala Days 2011 based on sbt 0.10.0 that gives an introduction to the configuration system in sbt 0.10.0 and later. See the documentation for current information.
- Google Code: hosts sbt 0.7.7 and earlier versions