James Mao wrote:
Hi Andrea,
The issue you mentioned is just the misc tools tests right?
Hi James,
No, source in misc tools depends on the core, to be precise:
org.apache.cxf.tools.misc.processor.AbstractWSDLToProcessor in
cxf-tools-misctools imports org.apache.cxf.wsdl11.WSDLDefinitionBuilder
from rt-core.
AND there is the unnecessary dependency of a test (can't remember which
one now) on cxf-rt-transports-jms and cxf-rt-binding-xml.
This breaks building successively in tools, then in rt. That must work IMO.
Andrea.
What about move all of those tests which depend on rt stuff to
wsdlto/tests? since wsdlto/tests is kind of system tests for tools and
it already depend on rt stuff.
And then remove the dependencies in the pom of misc tools.
Will that work for you?
[EMAIL PROTECTED] wrote:
Author: mmao
Date: Tue May 29 19:38:51 2007
New Revision: 542728
URL: http://svn.apache.org/viewvc?view=rev&rev=542728
Log:
CXF-658 Tool dependecies on runtime components
* Move xsd(s) from tools/common back to runtime
* Add plugin api to create the wsdl extensibility, to create the
binding/addresses which can be added into wsdl model
* Move service validator API, and move the XMLFormat validator to
xml binding
* Move testing resources into resources dir
* Remove system.out in tests
* Move some of tools tests which depend on rt to wsdlto/tests,
otherwise will have a cycle dependencies
Hi James,
This dependency should be removed also, e.g. by using test transport
and binding extensions instead of the real ones defined in the jms
and xml-binding module.
But a new dependency of cxf-tools-misctools on (WsdlDefinitionBuilder
in) cxf-rt-core was introduced.
I believe this goes unnoticed when building from the top by
shceduling the rt-core accordingly, but it does not work when when
you do a clean from the top, then an install in tools, then install
in rt ()which is what I do, and what should be supported).
Can you revisit these dependecies?
Andrea.
