Sorry , click the send too fast :
*I will try out to see if moving the code generation from testutils to
rt/frontend. will help .
Jim Ma wrote:
Thanks ,James .
I think creating a test module for java2ws will not help . Java2ws
tool supports spring configuration and depends on
the rt-frontend-simple .Introducing rt-frontend-simple will cause the
cyclic dependency .
I will try out to see if moving the code generation from testutils to
rt/frontend.
Cheers
Jim
James Mao wrote:
It's a problem of Maven.
To separate the project can solve the problem. we can push it to the
maven plugin repo, maybe?
But you will have the versioning problem, right?
Besides, the plugin depends on cxf tools which depends on cxf rt,
which in trun depends on the plugin (mostly for the tests), you
still have the cyclic dependency problem.
it's an egg chicken problem :(
You probably need create a test module.
As we discussed before, we should take some time to move the codegen
in the testutils to the rt/frontend, maybe solve the problem.
James
Hi all ,
I ran into a maven cyclic dependency problem when I added maven
Java2WS plugin to CXF.
The below message is the maven spit out when I execute mvn install
under trunk :
[INFO] The projects in the reactor contain a cyclic reference: Edge
between 'Vertex{label='org.apache.cxf:cxf-codegen-plugin'}' and
'Vertex{label='org
.apache.cxf:cxf-tools-java2ws'}' introduces to cycle in the graph
org.apache.cxf:cxf-tools-java2ws -->
org.apache.cxf:cxf-rt-frontend-simple --> org.a
pache.cxf:cxf-rt-bindings-xml -->
org.apache.cxf:cxf-rt-databinding-jaxb -->
org.apache.cxf:cxf-testutils --> org.apache.cxf:cxf-codegen-plugin
--> or
g.apache.cxf:cxf-tools-java2ws
[INFO]
------------------------------------------------------------------------
How can I resolve this cyclic dependency problem ? Can we move the
code-gen plugin into a separate project and separate code-gen
plugin release with CXF?
Could some one shed some light on this ?
Thanks
Jim
**
