|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
jaxws-maven-plugin failure on non Sun SDKHi to all,
We still get errors with jaxws-maven-plugin when were using a non Sun JDK. DEBUG] jaxws:wsgen args: [-d, C:\workspace\slib-ws-core-service\target\classes, -cp, C:\workspace\slib-ws-core-service\target\classes;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.7\jaxb-impl-2.1.7.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.1\saaj-impl-1.3.1.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0.1\sjsxp-1.0.1.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.2\mimepull-1.2.jar;c:\maven-repository\fr\slib\sx\canopee\slib-sx-canopee\2.0.0\slib-sx-canopee-2.0.0.pom;c:\maven-repository\fr\slib\sx\canopee\slib-jutils\2.0.0-9\slib-jutils-2.0.0-9.jar;c:\maven-repository\quartz\quartz\1.5.2\quartz-1.5.2.jar;c:\maven-repository\fr\slib\sx\canopee\slib-erable-framework\2.0.0-9\slib-erable-framework-2.0.0-9.jar;c:\maven-repository\com\sun\xml\ws\jaxws-tools\2.1.3\jaxws-tools-2.1.3.jar;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.3\jaxws-rt-2.1.3.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.6\jaxb-impl-2.1.6.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3\saaj-impl-1.3.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0\sjsxp-1.0.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.1\mimepull-1.1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-xjc\2.1.6\jaxb-xjc-2.1.6.jar;c:\maven-repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar, -wsdl, -r, C:\workspace\slib-ws-core-service\target\classes\fr\slib\xylos\ws\resources\wsdl, fr.slib.xylos.ws.service.CoreService] [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to execute wsgen Embedded error: com.sun.tools.apt.Main [INFO] ------------------------------------------------------------------------ [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute wsgen at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute wsgen at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:102) at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more Caused by: java.lang.NoClassDefFoundError: com.sun.tools.apt.Main at com.sun.tools.ws.wscompile.WsgenTool.buildModel(WsgenTool.java:194) at com.sun.tools.ws.wscompile.WsgenTool.run(WsgenTool.java:119) at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97) ... 19 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5 seconds [INFO] Finished at: Mon Jul 07 15:53:58 CEST 2008 [INFO] Final Memory: 12M/38M [INFO] ------------------------------------------------------------------------ Did the jaxws-maven-plugin developpers are watching this list, since I couldn't find JIRA on https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/ ? Regards --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKMore on this :
In the 1.10 pom file I could see : <profiles> <profile> <!-- This is only for non MAC OS X builds, hence the property below --> <id>default-tools.jar</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.5.0</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> With an IBM JDK ${java.vendor} is IBM Corporation. Sun Microsystems Inc. is only for ${java.specification.vendor} This profile add-on has been introduced to fix Apple JVM specific tools location but break this plugin now on IBM JDK, both Linux and Windows ;( --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKHow could we get the latest source ?
This url ask for login/password. https://svn.dev.java.net/svn/jax-ws-commons/tags/jaxws-maven-plugin-1.10 Thanks 2008/7/8 Henri Gomez <henri.gomez@...>: > > In the 1.10 pom file I could see : > > <profiles> > <profile> > <!-- This is only for non MAC OS X builds, hence the property below --> > <id>default-tools.jar</id> > <activation> > <property> > <name>java.vendor</name> > <value>Sun Microsystems Inc.</value> > </property> > </activation> > <dependencies> > <dependency> > <groupId>com.sun</groupId> > <artifactId>tools</artifactId> > <version>1.5.0</version> > <scope>system</scope> > <systemPath>${java.home}/../lib/tools.jar</systemPath> > </dependency> > </dependencies> > </profile> > </profiles> > > > With an IBM JDK ${java.vendor} is IBM Corporation. > > Sun Microsystems Inc. is only for ${java.specification.vendor} > > This profile add-on has been introduced to fix Apple JVM specific > tools location but break this plugin now on IBM JDK, both Linux and > Windows ;( > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKHenri Gomez wrote:
> How could we get the latest source ? > > This url ask for login/password. > use java.net id and password. But you could see online also https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/source-repository.html Jiut > https://svn.dev.java.net/svn/jax-ws-commons/tags/jaxws-maven-plugin-1.10 > > Thanks > > > 2008/7/8 Henri Gomez <henri.gomez@...>: > >> >> In the 1.10 pom file I could see : >> >> <profiles> >> <profile> >> <!-- This is only for non MAC OS X builds, hence the property below --> >> <id>default-tools.jar</id> >> <activation> >> <property> >> <name>java.vendor</name> >> <value>Sun Microsystems Inc.</value> >> </property> >> </activation> >> <dependencies> >> <dependency> >> <groupId>com.sun</groupId> >> <artifactId>tools</artifactId> >> <version>1.5.0</version> >> <scope>system</scope> >> <systemPath>${java.home}/../lib/tools.jar</systemPath> >> </dependency> >> </dependencies> >> </profile> >> </profiles> >> >> >> With an IBM JDK ${java.vendor} is IBM Corporation. >> >> Sun Microsystems Inc. is only for ${java.specification.vendor} >> >> This profile add-on has been introduced to fix Apple JVM specific >> tools location but break this plugin now on IBM JDK, both Linux and >> Windows ;( >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKDone.
BTW, could I suggest a fix for jaxws-maven-plugin ? Turn the current tools.jar activation from : <profiles> <profile> <!-- This is only for non MAC OS X builds, hence the property below --> <id>default-tools.jar</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.5.0</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> into <profiles> <profile> <!-- This is only for non MAC OS X builds, hence the property below --> <id>default-tools.jar</id> <activation> <file> <exists>${java.home}/../lib/tools.jar</exists> </file> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.5.0</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> For exemple IBM JDK ${java.vendor} is IBM Corporation. Under windows or Linux x86, you could switch from IBM to Sun SDK, but not on some specific OS/Hardware like AIX or Linux PowerPC. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKAny news about this suggestion ?
Thanks 2008/7/10 Henri Gomez <henri.gomez@...>: > Done. > > BTW, could I suggest a fix for jaxws-maven-plugin ? > > Turn the current tools.jar activation from : > > <profiles> > <profile> > <!-- This is only for non MAC OS X builds, hence the property below --> > <id>default-tools.jar</id> > <activation> > <property> > <name>java.vendor</name> > <value>Sun Microsystems Inc.</value> > </property> > </activation> > <dependencies> > <dependency> > <groupId>com.sun</groupId> > <artifactId>tools</artifactId> > <version>1.5.0</version> > <scope>system</scope> > <systemPath>${java.home}/../lib/tools.jar</systemPath> > </dependency> > </dependencies> > </profile> > </profiles> > > into > > <profiles> > <profile> > <!-- This is only for non MAC OS X builds, hence the property below --> > <id>default-tools.jar</id> > <activation> > <file> > <exists>${java.home}/../lib/tools.jar</exists> > </file> > </activation> > <dependencies> > <dependency> > <groupId>com.sun</groupId> > <artifactId>tools</artifactId> > <version>1.5.0</version> > <scope>system</scope> > <systemPath>${java.home}/../lib/tools.jar</systemPath> > </dependency> > </dependencies> > </profile> > </profiles> > > > For exemple IBM JDK ${java.vendor} is IBM Corporation. > > Under windows or Linux x86, you could switch from IBM to Sun SDK, but > not on some specific OS/Hardware like AIX or Linux PowerPC. > > Thanks > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKThe change looks fine.
thanks, Rama Pulavarthi Henri Gomez wrote: > Any news about this suggestion ? > > Thanks > > 2008/7/10 Henri Gomez <henri.gomez@...>: > >> Done. >> >> BTW, could I suggest a fix for jaxws-maven-plugin ? >> >> Turn the current tools.jar activation from : >> >> <profiles> >> <profile> >> <!-- This is only for non MAC OS X builds, hence the property below --> >> <id>default-tools.jar</id> >> <activation> >> <property> >> <name>java.vendor</name> >> <value>Sun Microsystems Inc.</value> >> </property> >> </activation> >> <dependencies> >> <dependency> >> <groupId>com.sun</groupId> >> <artifactId>tools</artifactId> >> <version>1.5.0</version> >> <scope>system</scope> >> <systemPath>${java.home}/../lib/tools.jar</systemPath> >> </dependency> >> </dependencies> >> </profile> >> </profiles> >> >> into >> >> <profiles> >> <profile> >> <!-- This is only for non MAC OS X builds, hence the property below --> >> <id>default-tools.jar</id> >> <activation> >> <file> >> <exists>${java.home}/../lib/tools.jar</exists> >> </file> >> </activation> >> <dependencies> >> <dependency> >> <groupId>com.sun</groupId> >> <artifactId>tools</artifactId> >> <version>1.5.0</version> >> <scope>system</scope> >> <systemPath>${java.home}/../lib/tools.jar</systemPath> >> </dependency> >> </dependencies> >> </profile> >> </profiles> >> >> >> For exemple IBM JDK ${java.vendor} is IBM Corporation. >> >> Under windows or Linux x86, you could switch from IBM to Sun SDK, but >> not on some specific OS/Hardware like AIX or Linux PowerPC. >> >> Thanks >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: jaxws-maven-plugin failure on non Sun SDKRama
Can you do the change ? Jitu Rama Pulavarthi wrote: > The change looks fine. > > thanks, > Rama Pulavarthi > > Henri Gomez wrote: >> Any news about this suggestion ? >> >> Thanks >> >> 2008/7/10 Henri Gomez <henri.gomez@...>: >> >>> Done. >>> >>> BTW, could I suggest a fix for jaxws-maven-plugin ? >>> >>> Turn the current tools.jar activation from : >>> >>> <profiles> >>> <profile> >>> <!-- This is only for non MAC OS X builds, hence the property >>> below --> >>> <id>default-tools.jar</id> >>> <activation> >>> <property> >>> <name>java.vendor</name> >>> <value>Sun Microsystems Inc.</value> >>> </property> >>> </activation> >>> <dependencies> >>> <dependency> >>> <groupId>com.sun</groupId> >>> <artifactId>tools</artifactId> >>> <version>1.5.0</version> >>> <scope>system</scope> >>> <systemPath>${java.home}/../lib/tools.jar</systemPath> >>> </dependency> >>> </dependencies> >>> </profile> >>> </profiles> >>> >>> into >>> >>> <profiles> >>> <profile> >>> <!-- This is only for non MAC OS X builds, hence the property >>> below --> >>> <id>default-tools.jar</id> >>> <activation> >>> <file> >>> <exists>${java.home}/../lib/tools.jar</exists> >>> </file> >>> </activation> >>> <dependencies> >>> <dependency> >>> <groupId>com.sun</groupId> >>> <artifactId>tools</artifactId> >>> <version>1.5.0</version> >>> <scope>system</scope> >>> <systemPath>${java.home}/../lib/tools.jar</systemPath> >>> </dependency> >>> </dependencies> >>> </profile> >>> </profiles> >>> >>> >>> For exemple IBM JDK ${java.vendor} is IBM Corporation. >>> >>> Under windows or Linux x86, you could switch from IBM to Sun SDK, but >>> not on some specific OS/Hardware like AIX or Linux PowerPC. >>> >>> Thanks >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| Free Forum Powered by Nabble | Forum Help |