Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-2119

Depenencies excluded in Gradle build files are not excluded in the generated Maven POMs

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.3, 5.4
    • Fix Version/s: 5.4
    • Component/s: None

      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).

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              hlship Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: