[
https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045719#comment-16045719
]
Hudson commented on MNG-6209:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-plugins #8993 (See
[https://builds.apache.org/job/maven-plugins/8993/])
[MASSEMBLY-858] don't declare m-assembly-p as extension: this is not normal
use, is not useful (and caused failure when MNG-6209 was fixed)
this shows that MNG-6209 won't break every build with previous m-assembl-p
versions: only builds that declare this plugin as extension, but who does that?
(hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1798339])
* (edit) maven-assembly-plugin/src/it/it-project-parent/pom.xml
> inconsistent activation of components from multiple extensions=true plugins
> ---------------------------------------------------------------------------
>
> Key: MNG-6209
> URL: https://issues.apache.org/jira/browse/MNG-6209
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Reporter: Igor Fedorenko
> Assignee: Igor Fedorenko
> Fix For: 3.5.1
>
>
> This is a regression introduced by the fix for MNG-5742. When multiple
> extensions=true plugins configured in the build, when mojos from one such
> plugin are executed, components from other extensions are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
