Hi,
on Friday I committed a change to cxf/trunk/systests/pom.xml for including the container-integration systests in the build, as they were (and still are) passing for me. Today I see they build failed on hudson https://hudson.apache.org/hudson/view/CXF/job/CXF-trunk-deploy/389/console, basically because the org.jvnet.jax-ws-commons:jaxws-grizzly-httpspi:jar:1.1 dependency is not found on the central repo (well, it's actually grizzly too), while I got the same locally from the http://download.java.net/maven/2/ repo which is also used here. What policy do we have for situations like this, if any ? Can I just add the java.net repo, or should we try to find out if we can have those artifacts pushed to central?
It would be really nice to keep those tests enabled..
Cheers
Alessio

--
Alessio Soldano
Web Service Lead, JBoss

Reply via email to