forked from JetBrains/bazel-bsp
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resolve Scala SDK independently for each target
This prepares us for changes in `rules_scala` that will allow customizing the Scala version for each target. In order to achieve that, we can no longer resolve the Scala SDK globally as the maximal version used. We need to use per-target info. Scala SDK will be still discovered based on the compiler class path. Now though we will look into one of a dep providers of a Scala toolchain, namely the `scala_compile_classpath` – a canonical place to put all compile-related jars. This change is backward-compatible, as the mentioned data is already available. It is also forward-compatible with the anticipated cross-build feature of `rules_scala`. (see: bazelbuild/rules_scala#1290) The aspect will produce additional data – namely few compiler classpath jars per Scala target.
- Loading branch information
Showing
4 changed files
with
31 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters