Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to rules_jvm_external 6.2, repin maven deps #183

Merged
merged 1 commit into from
Jul 10, 2024

Conversation

mbland
Copy link
Contributor

@mbland mbland commented Jul 8, 2024

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 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:

@mbland mbland self-assigned this Jul 8, 2024
- https://github.com/bazelbuild/rules_jvm_external/releases/tag/6.2

This new version resolves the issue mentioned in #182:

- bazel-contrib/rules_jvm_external#1189

Fixed by:

- bazel-contrib/rules_jvm_external#1122

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:

- https://blog.engflow.com/2024/06/27/migrating-to-bazel-modules-aka-bzlmod---the-easy-parts/#with-rules_jvm_external

Signed-off-by: Mike Bland <mbland@engflow.com>
@mbland mbland force-pushed the rules_jvm_external-6.2 branch from 85d1326 to cbbf59c Compare July 8, 2024 17:09
@mbland mbland merged commit 56191b6 into main Jul 10, 2024
3 checks passed
@mbland mbland deleted the rules_jvm_external-6.2 branch July 10, 2024 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants