[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

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

Type: Bug
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Duplicate Votes: 0


Given the following dependency declaration:

dependencies {
    compile 'axis:axis-jaxrpc:1.4'

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:

compile - Compile classpath for source set 'main'.
\--- axis:axis-jaxrpc:1.4
     \--- org.apache.axis:axis-jaxrpc:1.4

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:

  • 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 [ 25/Jan/17 ]

Work is now tracked here: https://github.com/gradle/gradle/issues/1256

Generated at Wed Jun 30 12:45:11 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.