[GRADLE-3301] Originating module with relocation assignment parsed from Maven POM is added to dependency graph Created: 14/May/15 Updated: 25/Jan/17 Resolved: 25/Jan/17
Given the following dependency declaration:
The corresponding POM of the module has the following relocation assignment:
Rendering the dependency report indicates that the originating module as well as the relocated module is added to the dependency graph:
Only the relocated module should be added.
|Comment by Mark Vieira (Inactive) [ 28/May/15 ]|
This problem is not limited do the dependency report. Confirmed that GradlePomModuleDescriptorParser naively adds the relocated artifact as a dependency of the original. When only a groupId relocation exists this is typically not a problem but in cases where artifactId is relocated you end up with multiple artifacts.
|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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 25/Jan/17 ]|
Work is now tracked here: https://github.com/gradle/gradle/issues/1256