[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069706#comment-17069706 ] Hudson commented on MNG-6209: - Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4 See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/ > 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 >Priority: Major > Fix For: 3.x / Backlog > > > 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 (v8.3.4#803005)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208095#comment-16208095 ] Hudson commented on MNG-6209: - SUCCESS: Integrated in Jenkins build maven-3.x #1672 (See [https://builds.apache.org/job/maven-3.x/1672/]) Revert "MNG-6209 better executeMojo thread context classloader" (stephen.alan.connolly: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=4b95ad9fce6dfe7eec2be88f5837e96c7fbd7292]) * (edit) maven-core/src/main/java/org/apache/maven/plugin/DefaultBuildPluginManager.java > 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.4.14#64029)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140435#comment-16140435 ] Vinay Shankar commented on MNG-6209: [~igorf] - No. The page at this link, https://issues.apache.org/jira/projects/MNG/versions/12338964, has two warnings. I was referring to them thinking they might be blocking the release of 3.5.1. I am just interested in the release of 3.5.1. > 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.4.14#64029)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140389#comment-16140389 ] Igor Fedorenko commented on MNG-6209: - Not sure I understand the question. The changes were reviewed and merged to master long time ago. Are you saying current 3.5.1 snapshot is still affected by the problem? > 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.4.14#64029)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140095#comment-16140095 ] Vinay Shankar commented on MNG-6209: [~igorf] - Could you please create a PR for the commits if they have not been merged yet? According to the link https://issues.apache.org/jira/projects/MNG/versions/12338964, the 3.5.1 release is pending due to unreviewed commits from MNG-6209. 3.5.0 has a bug (MNG-6240 and MDEPLOY-221) and a 3.5.1 release will be very useful. > 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.4.14#64029)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045889#comment-16045889 ] Hervé Boutemy commented on MNG-6209: yes: it was there a long time ago, near from the first import: not really tied to any change. I suppose it was in the early Maven days, when a lot of parts were moving and the classpath structure with realms was not so clear: flagging the plugin as extension was an easy insurance against any change, and did not seem to cause any serious issue this extensions plugins thread classpath change is a good opportunity of cleanup :) and we're lucky it finally does not hit normal users, but just cleans up plugin and ITs > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045710#comment-16045710 ] Hudson commented on MNG-6209: - SUCCESS: Integrated in Jenkins build maven-plugins #8992 (See [https://builds.apache.org/job/maven-plugins/8992/]) [MASSEMBLY-858] use plugin classloader instead of thread classloader fixes issues caused by MNG-6209 fix: but currently, every m-assembly-p from 2.2 to 3.0.0 using descriptor from classloader will fail with Maven 3.5.1... (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1798337]) * (edit) maven-assembly-plugin/src/main/java/org/apache/maven/plugins/assembly/io/DefaultAssemblyReader.java > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045708#comment-16045708 ] Hervé Boutemy commented on MNG-6209: I just tested: I removed the extension in m-assembly-p ITs and removed the plugin fix as expected, since the plugin is not extension, MNG-6209 does not make the ITs fail then good news: this fiw won't break normal builds from the past, but only builds that declare the m-assembly-p as extension = something that should not happen I think now we can close this issue as fixed without fear for compatibility with the past > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[
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
{{true}} 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037692#comment-16037692 ] Hervé Boutemy commented on MNG-6209: I looked into m-assembly-p history and found the commit in question: for MASSEMBLY-331 the change does not look related to real bug fixing, just a change that was apparently innocent... > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037505#comment-16037505 ] Igor Fedorenko commented on MNG-6209: - Agree with Hervé. Thread context classloader use is a bug in maven assembly plugin and needs to be fixed there. > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037399#comment-16037399 ] Hervé Boutemy commented on MNG-6209: since when is this thread classloader used by maven-assembly-plugin? It's a surprising choice. IMHO, the minimum will be to have a maven-assembly-plugin release before we ship Maven 3.5.1, and add this to release notes: this assembly plugin was fragile relying on thread context classloader without apparent real need, we'll just help users know the issue and fix when upgrading Maven to 3.5.1 > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[
https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037088#comment-16037088
]
Michael Osipov commented on MNG-6209:
-
I am not certain. The code remained the same for more than seven years now. The
descriptor can also be located in another JARs, but always on the plugin
classpath.
I did apply now this patch locally:
{noformat}
Index:
src/main/java/org/apache/maven/plugins/assembly/io/DefaultAssemblyReader.java
===
---
src/main/java/org/apache/maven/plugins/assembly/io/DefaultAssemblyReader.java
(revision 1797662)
+++
src/main/java/org/apache/maven/plugins/assembly/io/DefaultAssemblyReader.java
(working copy)
@@ -196,7 +196,7 @@
InvalidAssemblerConfigurationException
{
final InputStream resourceAsStream =
-
Thread.currentThread().getContextClassLoader().getResourceAsStream(
"assemblies/" + ref + ".xml" );
+getClass().getClassLoader().getResourceAsStream( "assemblies/" +
ref + ".xml" );
if ( resourceAsStream == null )
{
{noformat}
and it does work. So Igor, you idea was correct. [~hboutemy], [~igorf], what
bothers me now is that decriptor ref usecases with 3.5.1 will be broken when
shipped even if I address this issue in MASSEMBLY. Any thoughts?
> 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036921#comment-16036921 ] Igor Fedorenko commented on MNG-6209: - Why does assembly plugin use Thread.currentThread().getContextClassLoader() to retrieve assembly.xml descriptor? If the descriptor is located in the same jar as the plugin (or at least in the same classloader), getClass().getClassLoader() seems like the proper way to get the descriptor, no? > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[
https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036876#comment-16036876
]
Michael Osipov commented on MNG-6209:
-
You can simply take this
[IT|https://github.com/apache/maven-plugins/tree/trunk/maven-assembly-plugin/src/it/projects/mojo-configuration/manifest-with-mainClass]
and invoke as Maven Core IT. The key is about the {{descriptorRef}} this is
located in the same JAR and the plugin. It could be also on the plugin
classpath. This classpath is now gone and the descriptor (assembly.xml) cannot
be loaded:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:3.0.1-SNAPSHOT:single (assembly)
on project manifest-with-mainClass: Error reading assemblies: Descriptor with
ID 'jar-with-dependencies' not found -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:3.0.1-SNAPSHOT:single (assembly)
on project manifest-with-mainClass: Error reading assemblies: Descriptor with
ID 'jar-with-dependencies' not found
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:937)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error reading
assemblies: Descriptor with ID 'jar-with-dependencies' not found
at
org.apache.maven.plugins.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:447)
at
org.apache.maven.plugins.assembly.mojos.SingleAssemblyMojo.execute(SingleAssemblyMojo.java:61)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: org.apache.maven.plugins.assembly.io.AssemblyReadException:
Descriptor with ID 'jar-with-dependencies' not found
at
org.apache.maven.plugins.assembly.io.DefaultAssemblyReader.addAssemblyForDescriptorReference(DefaultAssemblyReader.java:210)
at
org.apache.maven.plugins.assembly.io.DefaultAssemblyReader.readAssemblies(DefaultAssemblyReader.java:125)
at
org.apache.maven.plugins.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:443)
... 23 more
[ERROR]
{noformat}
Is that enough for an IT for you?
> 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036858#comment-16036858 ] Igor Fedorenko commented on MNG-6209: - I am not familiar with maven assembly plugin implementation, sorry. Do you think you can provide Maven IT that shows the problem? > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969329#comment-15969329 ] Hudson commented on MNG-6209: - SUCCESS: Integrated in Jenkins build maven-3.x #1644 (See [https://builds.apache.org/job/maven-3.x/1644/]) MNG-6209 better executeMojo thread context classloader (ifedorenko: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=ec629f7d511eb910b4e80112a9fbe85ed8786f10]) * (edit) maven-core/src/main/java/org/apache/maven/plugin/DefaultBuildPluginManager.java > 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)
[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966247#comment-15966247 ] Igor Fedorenko commented on MNG-6209: - The proposed fix: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=53a2af8ee11fc3f4aa829193b99cde95a3f04735 The corresponding IT: https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=f476ac3d4567312dcd9ea0975ce5cba84ddcb1ec > 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 > > 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)
