Skip to content

Conversation

shs96c
Copy link
Collaborator

@shs96c shs96c commented Oct 5, 2025

Until now the maven and gradle resolvers have been linked into the same binary. While this is convenient, it means that people need to download dependencies they won't otherwise use.

This change breaks the resolvers into their own java_binary targets so that they can be referenced individually, thus reducing the amount of dependencies that need to be downloaded before resolution can begin.

After this change:

bazel query 'somepath(@regression_testing_maven//:pin, @gradle//...:*)'

returns an empty set.

Closes #1455

Until now the `maven` and `gradle` resolvers have been linked into the
same binary. While this is convenient, it means that people need to
download dependencies they won't otherwise use.

This change breaks the resolvers into their own `java_binary` targets
so that they can be referenced individually, thus reducing the amount
of dependencies that need to be downloaded before resolution can
begin.

After this change:

bazel query 'somepath(@regression_testing_maven//:pin, @gradle//...:*)'

returns an empty set.
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.

Setting resolver to maven attempts fetching Gradle binary
2 participants