[GRADLE-1805] Allow users to define custom dependency resolvers Created: 22/Sep/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: New Feature
Reporter: Dumitru Daniliuc Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Please add the ability for users to define custom dependency resolvers.

Comment by Adam Murdoch [ 22/Sep/11 ]

Can you give some more details of what you'd like to use custom dependency resolvers for?

Comment by Dumitru Daniliuc [ 23/Sep/11 ]

1. I'd like to be able to use custom parameters: group, name and version are not always enough, or do not always correspond to how dependencies are organized. (By the way, ModuleDependencyFactory needs to be fixed: if the 'group' or 'name' parameter is missing, it should not create a DefaultExternalModuleDependency, because that will throw a InvalidUserDataException; instead, ModuleDependencyFactory should throw a InvalidDependencyNotation exception, to allow other resolvers to try to process the notation.)

2. I have multiple places where my dependencies can be pulled from (artifact repository and local builds, for example). So I'd like to allow users to specify a rule like:

compile project: 'X', module: 'Y', version: 'Z'

without having to worry where the dependency is pulled from. And I would like to be able to implement a resolver that does something like this: if version Z of module Y of project X is checked out locally, then build it, and use /var/tmp/build/project_X/module_Y-Z.jar; otherwise, pull X_Y-Z.jar from the artifact repository.

Basically, I want to be able to decide how to resolve a dependency when I run build.gradle, not when I write it.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:04:49 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.