[GRADLE-1349] Improved behavior for chained Maven repositories Created: 25/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Issue Links:
Related
Related to GRADLE-1348 Transitive dependency not being pulle... Resolved

 Description   

Given this build script:

repositories {
  mavenCentral name:'jboss', urls:"http://repository.jboss.org/nexus/content/groups/public-jboss/"
}

dependencies {
  compile group:'org.hibernate', name:'hibernate-core', version:'3.6.0.Final'
}

Here, mavenCentral is mistakenly used instead of mavenRepo. What then happens is that Ivy doesn't find hibernate-core POM/Jar in Central, but nevertheless downloads the Jar from JBoss repository. Because it doesn't have a POM, Ivy doesn't do any transitive dependency management (without warning the user). After fixing the problem by replacing mavenCentral with mavenRepo, one still has to clear out the Ivy cache in order to get transitive dependency management back.

With this behavior, the problem is difficult to track down. Maybe the resolution behavior could be improved, e.g. by looking for the POM (not just for the Jar) in both repositories. Or one could issue a warning that no transitive dependency management is possible for hibernate-core.

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