sbt-scripted fails when using sbt 1.0.1 and coursier
See original GitHub issueI’m running:
- sbt 1.0.1
- coursier 1.0.0-RC11
When using sbt-scripted, I systematically get the following failure:
info] Error during sbt execution: Could not finder sbt launch configuration. Searched classpath for:
[info] /sbt.boot.propertiesUnspecified
[info] /sbt/sbt.boot.propertiesUnspecified
[info] /sbt.boot.properties
[info] /sbt/sbt.boot.properties
When I remove coursier from my list of global plugins, everything seems to behave as it should.
Here’s a repository containing the smallest reproduction I could make, and there’s the travis log that shows the same failure.
By contrast, this is the travis log when coursier is not enabled.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
sbt-coursier
sbt Native Packager conflict. If you use sbt-native-packager and encounter a compile error java.lang.NoClassDefFoundError: org/vafer/jdeb/ ...
Read more >sbt/sbt - Gitter
with 1.0, sbt seems to be unable to find the dependencies we have on the ... [error] unresolved dependency: org.scala-sbt#scripted-plugin;1.0.0: not found.
Read more >SBT preload failure - Stack Overflow
when i invoke sbt commands through jenkins pipeline, it fails... Below is the Jenkins pipeline code and failure log: docker.withRegistry(.
Read more >sbt - Scaladex
sbt is a build tool for Scala, Java, and more. ... Other links. Setup: Describes getting started with the latest binary release.
Read more >sbt Reference Manual — Testing sbt plugins
sbt comes with scripted test framework, which lets you script a build scenario. ... When you recompile, you should get an error because...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Confirmed, at least for my user case.
@dwijnand The default implementation of
sbtLauncher
makes assumptions about the order of things in the update report - in particular, it seems to expect the jar oforg.scala-sbt:sbt-launch
upfront. On the other hand, sbt-coursier doesn’t provide guarantees about the order of things in the update report (for now, at least).