You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2016/04/16 15:09:25 UTC
[jira] [Closed] (MNG-6002) Maven should not use compile
dependencies for plugins
[ https://issues.apache.org/jira/browse/MNG-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MNG-6002.
-------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
> 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
> Assignee: Robert Scholte
>
> 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)