I also have to add the explicit dependencies for jsr181 for the wsimport
plugin under r759207 and the continuum build is passing now.
Let me try to merge it into 1.x too.
Thanks,
Raymond
--------------------------------------------------
From: "Raymond Feng" <[email protected]>
Sent: Friday, March 27, 2009 8:28 AM
To: <[email protected]>
Subject: Re: 2.x continuum build fails due to jaxws pom.xml
Hi,
I was trying two possible fixes (workarounds) yesterday.
1) Add jsr181 as an explicit dependency in addition to jaxws-api (the
problematic pom is missing the transitive dependencies)
2) Reference jaxws-api-2.1-1 instead of jaxws-api-2.1. It breaks our
maven-eclipse-compiler and I fixed the issue in the
maven-plugins/trunk/maven-eclipse-compiler.
I have checked in the change for 1) into 2.x. Let me fire off a build to
see if it helps.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Friday, March 27, 2009 4:18 AM
To: <[email protected]>; <[email protected]>
Subject: Re: 2.x continuum build fails due to jaxws pom.xml
snip...
I wondered if a workaround could
be to publish the fixed up pom.xml's and jars in the Tuscany svn
repository we have at [3] using a new tuscany specific groupid,
This implication being that we fix out our dependencies to refer to
this new group id? We'd have to take care of any other transitive
dependencies also.
Doing a bit a googling it doesn't seem that you can influence the
respository search order without going to a repository manager or a
mirror so I don't have a better idea.
Simon
