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 in maven_install.json.
Finally, @shs96c noted to me in private that:
...with recent rules_jvm_external releases, all you need to update is bazel run @maven//:pin. There’s no need for the unpinned_maven repo any more.
I removed the unpinned_maven repo and ran REPIN=1 bazel run @maven//:pin to regenerate maven_install.json. This also removed the unpinned_maven entries from MODULE.bazel.lock.
I'll update this section of my Bzlmod migration blog post after merging this change:
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: