They seem to be publishing concurrently to
http://people.apache.org/repository/ws-commons/jars/
and
http://people.apache.org/repository/org.apache.ws.commons/jars/
The former is probably for legacy applications as the pom in the
trunk (at least for XmlSchema) now has a groupId of
org.apache.ws.commons
Some of our poms still refer to the old "ws-commons" and we should
change those.
I wiped all WS artifacts from by repo and get the same failure. I
updated the POM for tools to use a SNAPSHOT of XmlSchema but there
are some changes needed to the tools to react to the API changes in
XmlSchema - I have commented out the tools module for now.
--
Jeremy
On Sep 11, 2006, at 8:49 AM, Lee Surprenant wrote:
Jeremy,
Unless I am missing something, this latest problem is not directly
related to the XmlSchema problem above. Perhaps I should have made
that more clear. Never-the-less, I have explicity taken the latest
snapshot from http://people.apache.org/repository/http://
people.apache.org/repository/ws-commons/jars/
(note that this version is more recent than yours). Even with this
jar, I continue to obtain the error in the TuscanyJava2WSDLTestCase.
On a side-note, if I run with -Dmaven.test.skip=true, the build
executes "successfully."
thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
