[
https://issues.apache.org/jira/browse/MNG-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243089#comment-15243089
]
Karl Heinz Marbaise commented on MNG-6002:
------------------------------------------
Plugins define their own dependencies and the usual build define others and
also having different classloaders. Sometimes plugin authors don't define
correctly everything they need etc. which can result in such problems or define
in some cases dependencies as {{<scope>provided</scope>}} which is sometimes
useful etc. Unfortunately i can't take a look into the source code of the
plugin....(cause i can't find it)...
> 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)
