Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Maven classloader change
Hi Fred,

I'm seeing an issue with this 1.9 build embedding Maven 3.5.1 with the org.codehaus.mojo:jaxws-maven-plugin plugin:

Failure processing stdout. (org.codehaus.mojo:jaxws-maven-plugin:2.5:wsimport:jaxws-import:generate-sources)

org.apache.maven.plugin.MojoExecutionException: Failure processing stdout.
at org.codehaus.mojo.jaxws.AbstractJaxwsMojo.exec(AbstractJaxwsMojo.java:490)
at org.codehaus.mojo.jaxws.WsImportMojo.processLocalWsdlFiles(WsImportMojo.java:339)
at org.codehaus.mojo.jaxws.WsImportMojo.executeJaxws(WsImportMojo.java:292)
at org.codehaus.mojo.jaxws.MainWsImportMojo.executeJaxws(MainWsImportMojo.java:54)
at org.codehaus.mojo.jaxws.AbstractJaxwsMojo.execute(AbstractJaxwsMojo.java:386)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Failure processing stdout.
at org.codehaus.plexus.util.cli.CommandLineUtils.handleException(CommandLineUtils.java:333)
at org.codehaus.plexus.util.cli.CommandLineUtils.access$100(CommandLineUtils.java:34)
at org.codehaus.plexus.util.cli.CommandLineUtils$2.call(CommandLineUtils.java:242)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:108)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:75)
at org.codehaus.mojo.jaxws.AbstractJaxwsMojo.exec(AbstractJaxwsMojo.java:483)
... 36 more
Caused by: java.io.IOException: Failure printing line 'parsing WSDL...' to stdout.
at org.codehaus.plexus.util.cli.DefaultConsumer.consumeLine(DefaultConsumer.java:36)
at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:136)

I've created a test project showing this issue:
https://github.com/andham/m2e-mvn351-issue

My environment:
Windows 7 with Oracle JDK 1.8.0u144
Eclipse IDE for Java Developers (Oxygen) updated with m2e 1.9.0.20170913-1857

Can you reproduce?

/Anders

On Wed, Sep 13, 2017 at 9:36 PM, Fred Bricon <fbricon@xxxxxxxxx> wrote:
Hi,

please try this m2e 1.9 build embedding Maven 3.5.1 and check if it breaks your projects (or not):


In Eclipse:
- go to Help > Install New Software...
- select the m2e features you want to install,
- proceed with installation, restart

All m2e tests pass (https://ci.takari.io/job/m2eclipse-core-tests-maven-351/), I haven't seen any issue with it.


On Wed, Sep 13, 2017 at 12:24 PM, Fred Bricon <fbricon@xxxxxxxxx> wrote:
My initial tests look good, but I'll have to publish a CI build for others to test their projects. I'll have something up later today

On Wed, Sep 13, 2017 at 5:45 AM, Anders Hammar <anders@xxxxxxxxxx> wrote:
Hi again,

We'd like to close the vote on Friday 13:00 UTC. So feedback is very much appreciated before that. Especially if MNG-6275 [1] causes trouble for m2e. Igor had some concerns on this change.


/Anders

On Wed, Sep 13, 2017 at 9:31 AM, Anders Hammar <anders@xxxxxxxxxx> wrote:
Hi Fred,

Have you seen the voting thread wrt Maven 3.5.1 [1], which includes this classloader change? It would be great if it could be tested with m2e.


/Anders


On Tue, Sep 5, 2017 at 6:34 PM, Fred Bricon <fbricon@xxxxxxxxx> wrote:
@Richard, m2e 1.9 embeds Maven 3.5.0

The Maven team can now contact me about testing the new classloader changes.

On Sun, Sep 3, 2017 at 7:25 PM, Richard Vowles <richard@xxxxxxxxxxxxxxxxxxxxx> wrote:
The Eclipse version of Maven is so far behind the feature set of Maven, is it worth bothering?

On Sun, Sep 3, 2017 at 10:56 PM, Anders Hammar <anders@xxxxxxxxxx> wrote:
Hi,

The Apache Maven team is working on a classloader change so we'd like to have some testing by people who are embedding Maven and could have issues with this change.

More information is available in the info mail [1] on the Maven users mailing list. Please note that we're asking for a contact person from your project.
Thanks,
/Anders

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev



--
---
Richard Vowles,
Groovy, Java, _javascript_, AngularJS - Contract Software for Hire!

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev



--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev





--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5



--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5

Back to the top