[GRADLE-2812] Pom with relocation to a different version is not correctly handled Created: 26/Jun/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 11


As reported in a comment by 'dlethin', the POM for "xml-apis:xml-apis:2.0.2" is not correctly handled (http://forums.gradle.org/gradle/topics/gradle_does_not_report_missing_failed_artifact_downloads). This pom simply relocates to a different module version: same groupId and artifactId.

Comment by Daz DeBoer [ 11/Oct/13 ]

Test comment only: please ignore

Comment by mark petrovic [ 15/Oct/13 ]

This sounds very similar to what I've reported in this forum thread:


Comment by Endre Stølsvik [ 20/Feb/14 ]

Isn't this the same problem that is underlying here?

Comment by Thad Guidry [ 27/Oct/15 ]

Pom with relocation to a different groupId is also not working - http://repo1.maven.org/maven2/jug/jug/2.0.0/jug-2.0.0.pom
and I must use DependencyResolveDetails to workaround 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:32:10 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.