You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no compiler avoidance for Scala multi project builds.
Making a one line change such as adding a comment in a project that depend on it to be rebuilt.
There's no incremental compilation for the upstream projects either making it painful to do a simple change and quickly run some tests.
Expected Behavior
Scala uses the @CompilerClasspath similarly to Java to detect ABI compatible changes and skips re-building upstream projects.
Current Behavior
There's no compiler avoidance for Scala.
Context
We switched to building a large multi project Scala project with Gradle and have been mostly happy with it, but ran into some challenges for local development in small iterations of changing a few lines and running tests. We are working around these by using bloop and the bloop Gradle integration, but we'd rather use a single build tool with a single IDE setup. We use IntelliJ so our IDE builds default to Gradle too.
The text was updated successfully, but these errors were encountered:
@jbartok excited to see this get some traction this is still super important for us!
Please see this sample project, it uses Java classes instead of Scala but compiles them with the Scala plugin, so they behave like Scala classes for the purposes of this issue: scala-sample.tar.gz
big-guy
changed the title
Simple changes in a scal multi poject build take very long to compile preventing quick iteration
Simple changes in a scala multi project build take very long to compile preventing quick iteration
Sep 15, 2021
There's no compiler avoidance for Scala multi project builds.
Making a one line change such as adding a comment in a project that depend on it to be rebuilt.
There's no incremental compilation for the upstream projects either making it painful to do a simple change and quickly run some tests.
Expected Behavior
Scala uses the
@CompilerClasspath
similarly to Java to detect ABI compatible changes and skips re-building upstream projects.Current Behavior
There's no compiler avoidance for Scala.
Context
We switched to building a large multi project Scala project with Gradle and have been mostly happy with it, but ran into some challenges for local development in small iterations of changing a few lines and running tests. We are working around these by using bloop and the bloop Gradle integration, but we'd rather use a single build tool with a single IDE setup. We use IntelliJ so our IDE builds default to Gradle too.
The text was updated successfully, but these errors were encountered: