Update to rules_jvm_external 6.2, repin maven deps #183
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.
Details:
This new version resolves the issue mentioned in #182:
Fixed by:
Per my comment on that issue, source JARs are no longer fetched without explicitly setting
fetch_sources = True
. This is why they no longer appear inmaven_install.json
.Finally, @shs96c noted to me in private that:
I removed the
unpinned_maven
repo and ranREPIN=1 bazel run @maven//:pin
to regeneratemaven_install.json
. This also removed theunpinned_maven
entries fromMODULE.bazel.lock
.I'll update this section of my Bzlmod migration blog post after merging this change: