Support not bundling SemanticDB files #49
Closed
Conversation
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
jadenPete
force-pushed
the
support-not-bundling-semanticdb-files
branch
from
e32400d to
c35b45a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an attempt to recreate these changes in this repository. Unlike
bazelbuild/rules_scala's SemanticDB support, these changes don't check that the SemanticDB compiler plugin is loaded if we're working with Scala 2. Instead, it's assumed that if the user sets thesemanticdb_bundleScalaConfigurationparameter toFalse, they'll add the plugin. If they don't, the build will fail.