[GRADLE-1574] transitive = false should produce excludes for each dependency in POM Created: 26/May/11  Updated: 29/Mar/16  Resolved: 29/Mar/16

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: 2.14-rc-1

Type: Bug
Reporter: Luke Daley Assignee: Pepper Lebeck-Jobe
Resolution: Fixed Votes: 7


Using transitive = false produces incorrect poms because excludes are not added to the POM for all deps.

Unfortunately, maven doesn't support wildcards (http://jira.codehaus.org/browse/MNG-3832) so an explicit exclude is going to be needed for all deps.

Comment by Graeme Rocher [ 01/Aug/11 ]

FYI we implemented this is the Grails release plugin by resolving dependencies without excludes (and without downloading jars) and then generating the POM based on the metadata:


A similar solution is needed for Gradle's uploadArchives / POM generation task

Comment by Michael Böckling [ 14/Feb/12 ]

We just hit this one, too. Graeme's solution looks fine - any chance to get this in the next release?

Comment by Daz DeBoer [ 10/Aug/15 ]

https://github.com/gradle/gradle/pull/484 provides a patch for this issue. With appropriate integration test coverage we should be able to merge the PR and fix this issue.

Comment by Sandu Turcan [ 14/Feb/16 ]

A newer version of the PR is here: https://github.com/gradle/gradle/pull/570

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