I'm definitely not seeing this with the latest CXF code. The older 2.1.x version of CXF might be problematic due to the very old versions of some of the ws deps that may have defined that.
If you are having this issue with trunk or 2.7.x, it sounds like you have some bad poms in your ~/.m2/repository directory someplace. In your ~/.m2/repository directory, can you run: find . -name "*.pom" | xargs grep ws.zones.apache.org find . -name "*.pom" | xargs grep apache-ws-snapshots2 and see if it find anything? If so, try deleting those artifacts (likely delete the entire groupId or artifactId directory for anything it finds) and rebuilding and hope it grabs the appropriate stuff from central. Dan On Apr 22, 2013, at 5:23 PM, "Nuthalapati, Ramesh" <[email protected]> wrote: > Hello, > > Has any one tried using CXF (old version 2.1.3 and latest versions) along > with Maven 3.0.5 ? > > I see this message always > > {code} > > [WARNING] Failure to transfer > commons-logging:commons-logging/maven-metadata.xml from > http://ws.zones.apache.org/repository2/ was cached in the local repository, > resolution will not be reattempted until the update interval of > apache-ws-snapshots2 has elapsed or updates are forced. Original error: Could > not transfer metadata commons-logging:commons-logging/maven-metadata.xml > from/to apache-ws-snapshots2 (http://ws.zones.apache.org/repository2): > Connection to http://ws.zones.apache.org refused > > > {code} > > The build doesn't fail but takes a while trying to fetch that and it always > does every time I build, looks like CXF has a repository reference in its POM > ? > > This works great with maven 2.2.1. > > Any thoughts ? > > Thanks ! > > > > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
