[GRADLE-3390]  Module replacement not reflected in publication metadata Created: 02/Feb/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Won't Fix Votes: 2

Known Issue Of:


Reported in forum: https://discuss.gradle.org/t/module-replacement-not-reflected-in-publication-metadata/14113

We want to define project and enterprise-wide module replacements to avoid conflicts due to changed coordinates, however they're not reflected in the published metadata. Reduced case is:

repositories {

dependencies {
    compile 'com.google.collections:google-collections:1.0'
    compile 'com.google.truth:truth:0.28' // Has a guava dependency
    modules {
        module("com.google.collections:google-collections") {

publishing {
    repositories {
        ivy {
            url 'build/testivyrepo'
            name 'testivy'
    publications {
        ivyPublish(IvyPublication) {
            from components.java

Results in:

  <dependency org="com.google.collections" name="google-collections" rev="1.0" conf="runtime-&gt;default"/>
  <dependency org="com.google.truth" name="truth" rev="0.28" conf="runtime-&gt;default"/>


runtime - Runtime classpath for source set 'main'.
+--- com.google.collections:google-collections:1.0 -> com.google.guava:guava:18.0
\--- com.google.truth:truth:0.28
     +--- com.google.guava:guava:18.0
     \--- junit:junit:4.10
          \--- org.hamcrest:hamcrest-core:1.1

Comment by Danny Thomas [ 10/May/16 ]

This also means that even basic conflict resolution isn't reflected - the dependencies are configured when you call `from components.java`. I've written some failing tests here, but looks like a major overhaul of components and publishing to get correct results:


Comment by Danny Thomas [ 10/May/16 ]

We've added a workaround to our publishing plugins, replacing the requested module details with the selected module details:

See https://github.com/nebula-plugins/nebula-publishing-plugin for details.

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