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

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676401#comment-13676401 ] 

Howard M. Lewis Ship commented on TAP5-2119:
--------------------------------------------

>From this page (at the bottom):

http://www.gradle.org/docs/current/userguide/maven_plugin.html

    Gradle exclude rules are converted to Maven excludes if possible. Such a conversion is possible if in the Gradle exclude rule the group as well as the module name is specified (as Maven needs both in contrast to Ivy). Per-configuration excludes are also included in the Maven POM, if they are convertible.


                
> Depenencies excluded in Gradle build files are not excluded in the generated Maven POMs
> ---------------------------------------------------------------------------------------
>
>                 Key: TAP5-2119
>                 URL: https://issues.apache.org/jira/browse/TAP5-2119
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.3, 5.4
>            Reporter: Howard M. Lewis Ship
>            Priority: Critical
>              Labels: build, dependencies
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira