[GRADLE-712] Way to either override repositories specified in a project or to inject repositories ahead of those specified in a project Created: 21/Oct/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Steve Ebersole Assignee: Unassigned
Resolution: Won't Fix Votes: 10


 Description   

For OSS libraries, the build should JustWork when checked out. This would mean needing to include repository information in the project itself.

However, in many cases an individual developer would rather point to an "artifact manager" (Artifactory, Nexus, etc) for artifact resolution. currently this is not really possible since even though you can add repositories into the proect there is no way to prepend them; they would be appended and the project specified ones would win.

Ideally, this would be allowed system wide (aka ~/.gradle/init.gradle or similar)

 Comments   
Comment by Steve Ebersole [ 21/Oct/09 ]

A mirrorOf approach similar to what maven allows would work as well. In Maven, the user simply says that the artifact manager is a mirror of the central repository and maven will then try to resolve all artifact urls on central against the artifact manager mirror. Personally I think the injection + prepending approach is much nicer, but just wanted to point out another potential option

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 11:36:54 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.