[TAP5-2119] Depenencies excluded in Gradle build files are not excluded in the generated Maven POMs

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.3, 5.4
• Fix Version/s: 5.4
• Labels: build dependencies
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 28/May/13 23:40
• Updated: 16/Jul/13 16:34
• Resolved: 16/Jul/13 16:34

Description

This is particularly noticeable for tapestry-wro4j which depends on wro4j which has a huge number of transitive dependencies; we exclude many of those in the Gradle build, but this is not visible in the generated Maven POM, so end-user applications have to apply a lot of excludes (in Maven or Gradle).