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

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 5.3, 5.4
    • 5.4
    • 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

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hlship Howard Lewis Ship
            hlship Howard Lewis Ship
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment