[GRADLE-1796] Update user guide to explain how to get POMs from multiple Maven repos Created: 14/Sep/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-4
Fix Version/s: None

Type: Improvement
Reporter: Matt Callanan Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

As a Maven refugee I want to be able to get my dependency POMs from multiple Maven repos for the reasons discussed in GRADLE-1794. I found it difficult to understand how to do this from this doco. Please add something like the following:

Your company may deploy its artifacts to an internal repository and cache external dependencies in a separate repository. The POMs in your "internal" repository may depend on the POMs in the "external" repository. If POMs for dependencies are located in multiple Maven repositories, you can say:

Example NNN. Adding additional Maven repositories for POM files

build.gradle
repositories {
    mavenRepo urls: "http://repo.mycompany.com/internal"
    mavenRepo urls: "http://repo.mycompany.com/external"
}

Gradle will use both URLs to look for POMs and JARs.

 Comments   
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:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.