Actually, probably the best thing you could do is boil the problem down
to the simplest build you can think of that expresses the problem, and
file a JIRA ticket with the project attached. Then, let me know what the
JIRA # is, and I'll have a look. I can put it up on the debugger to see
why the paths are getting crossed up, if that's what's going on.
Unfortunately, I don't really know enough about how the CXF plugin works
to do much in the way of debugging remotely.
Thanks,
-john
nicolas de loof wrote:
I get an issue with 2.0.10 RC9 and CXF plugin -this works with 2.0.9 :
[INFO] [cxf-codegen:wsdl2java {execution: generate-sources}]
19 ao¹t 2008 11:08:16 org.apache.cxf.tools.wsdlto.core.PluginLoader
loadPlugin
INFO: Loading plugin
jar:file:/D:/platina/repository/org/apache/cxf/cxf-tools-wsdlto-databinding-jaxb/2.0.8/cxf-tools-ws
dlto-databinding-jaxb-2.0.8.jar!/META-INF/tools-plugin.xml
19 ao¹t 2008 11:08:17 org.apache.cxf.tools.wsdlto.core.PluginLoader
loadPlugin
INFO: Found 1 databindings in <jaxb> plugin.
19 ao¹t 2008 11:08:17 org.apache.cxf.tools.wsdlto.core.PluginLoader
loadPlugin
INFO: Loading <jaxb> databinding from <jaxb> plugin.
19 ao¹t 2008 11:08:17 org.apache.cxf.tools.wsdlto.core.PluginLoader
loadPlugin
INFO: Loading plugin
jar:file:/D:/platina/repository/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/2.0.8/cxf-tools-wsdl
to-frontend-jaxws-2.0.8.jar!/META-INF/tools-plugin.xml
19 ao¹t 2008 11:08:17 org.apache.cxf.tools.wsdlto.core.PluginLoader
loadPlugin
INFO: Found 1 frontends in <jaxws> plugin.
19 ao¹t 2008 11:08:17 org.apache.cxf.tools.wsdlto.core.PluginLoader
loadPlugin
INFO: Loading <jaxws> frontend from <jaxws> plugin.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] trace
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: trace
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:697)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:54
2)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:521)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:373)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:334)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:185)
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:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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: trace
at
org.apache.cxf.maven_plugin.WSDL2JavaMojo.processWsdl(WSDL2JavaMojo.java:334)
at
org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:228)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:672)
... 16 more
Caused by: java.lang.NoSuchMethodError: trace
at org.apache.commons.logging.impl.SLF4JLog.trace(SLF4JLog.java:96)
at
org.springframework.core.CollectionFactory.createConcurrentMapIfPossible(CollectionFactory.java:187)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.<init>(DefaultSingletonBeanRegistry.ja
va:82)
The CXF plugin seems to use my project dependencies (as I'm using slf4j) for
classpath during jaxb code generation
I ran the build with -X to compare dependency resolution trees but did not
found any change...
Maybe this is cause by some classloader conflict ?
What could I do to investigate more ?
2008/8/19 Martin Höller <[EMAIL PROTECTED]>
On Monday 18 August 2008 John Casey wrote:
Please, if you have the time, take 2.0.10-RC9 for a spin and tell us
what you think!
Works without any problems here.
- martin
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
