[2.x] fix: Support alternative Scala lib directories for scalaHome #1630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix scalaHome support for Scala 2.13/3 build directories
Fixes sbt/sbt#7477
The Problem
When using
scalaHomewith a Scala checkout (e.g., for testing local Scala changes), sbt fails with:This happens because zinc expects Scala jars in
$scalaHome/lib/, but:$scalaHome/build/pack/lib/after runningdist/mkPack$scalaHome/dist/target/pack/lib/The Fix
Update
ScalaInstance.scalaLib()to check multiple candidate directories:lib/(traditional/installed Scala)build/pack/lib/(Scala 2.13 afterdist/mkPack)dist/target/pack/lib/(Scala 3 builds)Also update
libraryJar()to support both:scala-library.jarscala3-library_3-*.jarTesting
With this fix, the following now works without the symlink workaround:
After running
dist/mkPackin the Scala checkout,sbt compileandsbt runwork correctly.