mirror of https://github.com/sbt/sbt.git
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. |
||
|---|---|---|
| .. | ||
| Docs.scala | ||
| Proguard.scala | ||
| Release.scala | ||
| Sbt.scala | ||
| Status.scala | ||
| Sxr.scala | ||
| Transform.scala | ||
| Util.scala | ||
| build.properties | ||
| p.sbt | ||