[
https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045705#comment-16045705
]
Hervé Boutemy commented on MNG-6209:
------------------------------------
I created and fixed MASSEMBLY-858: whatever we do, this plugin should not use
thread classloader
then I was worried about one question: with MNG-6209 fixed in Maven 3.5.1, does
that mean that any component already released with a version of m-assembly-p <=
3.0.0 will fail when loading a descriptor from a jar file? This would make
Maven 3.5.1 quite unusable to rebuild anything already released (then with a
failing m-assembly-p)
then I just found that m-assembly-p was declaring
{{<extension>true</extension>}} in its parent pom: this is what cause the
MNG-6209 fix to break the plugin. But in real life, who declares m-assembly-p
as extension plugin? Why are these its doing so?
If my analysis is confirmed, that would make Maven 3.5.1 usable with old
m-assembly-p versions: that would be a good news.
WDYT?
> 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)
