maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6002) Maven should not use compile dependencies for plugins
Date Fri, 15 Apr 2016 15:38:25 GMT

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

Karl Heinz Marbaise commented on MNG-6002:
------------------------------------------

As i said i can't  take a look into the source of the plugin if so maybe i could say more
....

> Maven should not use compile dependencies for plugins
> -----------------------------------------------------
>
>                 Key: MNG-6002
>                 URL: https://issues.apache.org/jira/browse/MNG-6002
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.3.9
>            Reporter: Jostein Gogstad
>
> Plugins and build dependencies are both subject to the same resolution of transitive
dependencies. This is problematic when plugins require newer dependencies than the build,
or vice versa. [This issue|https://ecosystem.atlassian.net/browse/MJF-251] in Atlassian's
jgit-flow plugin is an example where the plugin fails whenever the application depends transitively
on {{xerces}}.
> It should be possible to separate dependencies required for running the build from the
dependencies required for the actual build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message