What is the failure that you're seeing here? The changes look appropriate since the contents of maven/1 and maven/2 are now in Central, so removing those repo declarations should have no effect.
On Fri, Aug 19, 2011 at 10:18 AM, Blaney, Kyle (Kyle) <kbla...@avaya.com> wrote: > We recently encountered a strange Maven build error and the root cause turned > out to be that the com.sun.jersey:jersey-project:1.1.4:pom artifact differs > on Maven Central and java.net. In particular, on java.net > (http://download.java.net/maven/2/com/sun/jersey/jersey-project/1.1.4/jersey-project-1.1.4.pom) > the pom.xml defines two repositories (http://download.java.net/maven/1 and > http://download.java.net/maven/2) and the same two plugin repositories, while > on Maven Central > (http://search.maven.org/remotecontent?filepath=com/sun/jersey/jersey-project/1.1.4/jersey-project-1.1.4.pom) > the pom.xml only defines the second plugin repository; there are no > repositories defined. > > Is there a recommended way to reconcile the differences in a non-SNAPSHOT > numbered artifact between Maven Central and java.net so that others don't > experience my pain? > > Kyle Blaney > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
