compiler-bridge recompiled for every scripted test when cross building
See original GitHub issueWhen running scripted from an sbt 0.13.16 build, cross building against sbt 1.0, the Scala 2.12 compiler bridge seems to be being recompiled for every scripted test (that does compilation). It doesn’t happen when running scripted against sbt 0.13.16 with sbt 0.13.16, just when it’s a different sbt (or probably rather scala) version.
Example output shown in every scripted test that invokes compile:
[info] [info] Non-compiled module 'compiler-bridge_2.12' for Scala 2.12.3. Compiling...
[info] [info] Compilation completed in 9.008s.
9 seconds per scripted test (a lot longer on travis) is not ideal.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:14 (13 by maintainers)
Top Results From Across the Web
sbt Reference Manual — Combined Pages
sbt is a build tool for Scala, Java, and more. ... Use staged releases to test across large projects of independent releases before...
Read more >How to re-use compiled sources in different machines
- stage 1: Use SBT to compile Scala project into java bitecode using sbt compile We compile the test sources in the same...
Read more >Building and testing sbt plugins - Roman Timushev
The next step is writing scripted tests, which can verify how your ... you pay a noticeable penalty of sbt initialization for every...
Read more >Build Scripts - The Cargo Book
By default, Cargo will re-run the build script if any of the files in the package ... cargo:rustc-link-arg-tests=FLAG — Passes custom flags to...
Read more >The Scala Plugin - Gradle User Manual
To use the Scala plugin, include the following in your build script: Example 1. ... All the Scala source directories can contain Scala...
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 Free
Top 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
This should be the default.
I agree. The setting of
sbt.global.base
(inRemoteSbtCreator.scala
) should be only for sbt’s self-usage.