The continuum build of the 2.x code is failing [1] due to the jaxws bad pom.xml in the maven repository issue described in [2], and we've had users hit the same problem as well so it would be really nice to find a way to fix or work around it. 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, can anyone see and issues with doing that, or anyone have any other ideas about how we could fix this?
...ant [1] http://vmbuild.apache.org/continuum/buildResult.action?buildId=174362&projectId=2214&projectGroupId=19 [2] http://mail-archives.apache.org/mod_mbox/tuscany-dev/200802.mbox/%3c75283b3766d4410c96d3a877429f0...@rfengt60p%3e [3] https://svn.apache.org/repos/asf/tuscany/maven/
