I'm afraid you are hitting a known limitation of the incubating `maven-publish` plugin. I expect this limitation to go away before the plugin gets promoted.

Any Jira I can watch?

Does this work yet in any version of Gradle?

Any word on this yet?

Any news? I just ran into this same problem. Was able to work around it by moving all but one of the publications into a sub-project, but it's a pretty ugly solution. Also a bit worried that this issue was reported almost 2 years ago and there doesn't seem to have been any progress.

A workaround which I found for this is not to publish the artifact using the default provided ie. dont use - *components.java
The only drawback is you would need to prepare the pom file dependencies manually.

*E.g.
maven(MavenPublication)

Should be changed to

maven(MavenPublication)

+1 on this issue. It's been open for quite some time..

+1 from me too! This product seems unmaintained

@vnikhil@gmail.com could you elaborate on your example?
How do you create that pom entry with the dependencies?

I've applied the following workaround which seems to work fine until now:

publishing {
    publications {
        java(MavenPublication) {
             artifact jar

             // other stuff - skipped for readability

                pom.withXml {
                    def dependenciesNode = asNode().appendNode('dependencies')

                    configurations.runtime.allDependencies.each {
                        if (it.group != null && it.name != null) {
                            def dependencyNode = dependenciesNode.appendNode('dependency')
                            dependencyNode.appendNode('groupId', it.group)
                            dependencyNode.appendNode('artifactId', it.name)
                            dependencyNode.appendNode('version', it.version)

                            if (it.excludeRules.size() > 0) {
                                def exclusionsNode = dependencyNode.appendNode('exclusions')
                                it.excludeRules.each { rule ->
                                    def exclusionNode = exclusionsNode.appendNode('exclusion')
                                    exclusionNode.appendNode('groupId', rule.group)
                                    exclusionNode.appendNode('artifactId', rule.module)
                                }
                            }
                        }
                    }
                }
        }
    }
}

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!

I still "advocate" for this issue. Its a big hurdle in the Hibernate build.

I am still inhibited by this bug - as in, I have to work around it.

Is this issue already moved to GitHub?
Also from my side this bug is still important, and a fix would be more then welcome so that I can remove my "workarounds".

I also advocate for this issue.

Will we be getting any kind of notification of the new associated GitHub issue? I have a few issues that should be moved (that I replied to) that I have no idea if they have been moved.

Can someone provide a link to the github version of this issue? I can't seem to find it on https://github.com/gradle/gradle/issues

@Everyone: I have cloned this issue on GitHub at https://github.com/gradle/gradle/issues/1061 — please subscribe and give your :+1:s there.

@Steve: please confirm that you got a notification for this.

Moved to https://github.com/gradle/gradle/issues/1061

Thanks Eric, I did. I'll apply my +1000 there