Implement direct dependency tags for maven external targets #141
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.
Proposed Changes
This change generates tags for maven artifacts that can be used to do classpath reduction on Bazel side. This builds on top of existing implementation where direct dependency information is embedded in tags and our Bazel fork uses it to do classpath reduction.
Design Decisions
WORKSPACE
, have@maven// prefix
.With this change, we can enable compiling with direct dependencies for both internal and external targets which brings significant performance increase for both clean and incremental builds.