Eclipse Community Forums: Eclipse Scout » Neon: jaxws-maven-plugin error in an Mars.2 IDE

Home » Eclipse Projects » Eclipse Scout » Neon: jaxws-maven-plugin error in an Mars.2 IDE

Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1727273]

Mon, 21 March 2016 12:26

Eclipse User

I am trying to set up the "Scout Demo App" project using Oomph.
I am using the "Eclipse IDE for Scout Committers" as base installation and I am having trouble with the "jaxws-maven-plugin" (for WSDL Files) if I use the Mars version. In the materialized "org.eclipse.scout.docs.snippets" I get an Error marker at line 111 (see also the screenshot):

Invocation of com.sun.tools.ws.wscompile.WsimportTool failed - check output (org.codehaus.mojo:jaxws-maven-
 plugin:2.4:wsimport:wsimport-1:generate-sources) org.apache.maven.plugin.MojoExecutionException: Invocation 
 of com.sun.tools.ws.wscompile.WsimportTool failed - check output at 
 org.codehaus.mojo.jaxws.AbstractJaxwsMojo.exec(AbstractJaxwsMojo.java:488) at 
 org.codehaus.mojo.jaxws.WsImportMojo.processLocalWsdlFiles(WsImportMojo.java:340) at 
 org.codehaus.mojo.jaxws.WsImportMojo.executeJaxws(WsImportMojo.java:289) at 
 org.codehaus.mojo.jaxws.MainWsImportMojo.executeJaxws(MainWsImportMojo.java:51) at 
 org.codehaus.mojo.jaxws.AbstractJaxwsMojo.execute(AbstractJaxwsMojo.java:389) at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) 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:176) 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:176) 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:176) 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:734) at 
 org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) at 
 org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) at 
 org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) at 
 org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) at 
 org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) at 
 org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at 
 org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at 
 org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Where can I get more information? Logs, Stacktrace...

I cannot reproduce it using the Neon version of the IDE as base version.

Attachment: screenshot.png
(Size: 69.33KB, Downloaded 609 times)

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1728065 is a reply to message #1727273]

Wed, 30 March 2016 13:06

Eclipse User

I got the same error in a Scout EPP, Neon.M6 Version

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1728197 is a reply to message #1728065]

Thu, 31 March 2016 15:46

Eclipse User

I could not precisely verify it, but I think that the Java version is the problem. I think that I solve this problem by using a newer java version.
(In my case it works with the Java Version 1.8.0_66. I do not know what is the minimal required version).

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1754629 is a reply to message #1727273]

Tue, 21 February 2017 02:45

Eclipse User

I am running Java1.8.0_121. Still i am facing the same issue. There must be some other problem behind it.

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1754802 is a reply to message #1754629]

Wed, 22 February 2017 10:01

Eclipse User

I recommend using Neon.2 (or Neon.3 in a few weeks) Version of Eclipse IDE.

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1756177 is a reply to message #1754629]

Mon, 13 March 2017 10:32

Eclipse User

The problem seems to be that the pom for relies on java.home environment variable to be set correctly. There (slightly) more details in the error log view:

The POM for com.sun.xml.ws:jaxws-rt:jar:2.2.10 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details

Starting Eclipse with the JRE of the JDK installation helped for me, see also http://stackoverflow.com/a/27464117/546188

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1758839 is a reply to message #1756177]

Mon, 03 April 2017 11:47

Eclipse User

I've got the same error in Eclipse Neon. By adding "-consoleLog" to the eclipse.ini I could see the error details happend during the wsimport (btw it was a simple error in my wsdl file).

Re: Neon: jaxws-maven-plugin error in an Mars.2 IDE [message #1766566 is a reply to message #1727273]

Fri, 23 June 2017 03:00

Eclipse User

it seems your maven goal of wsimport failed and no stub class files generated

1. click Run as | maven build.. | with goal <groupId>:<artifactId>:<goals>
in your case:
org.codehaus.mojo:jaxws-maven-plugin:wsimport

2. eclipse will download required libraries if needed and generate the files to target/generated-sources/wsimport

3. refresh the said folder in the project to trigger building those files if necessary

hth

Previous Topic:	How to create a Dashboard in a TablePage
Next Topic:	Set SearchForm-Field from the TablePage-Value

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Nov 05 07:53:59 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter