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

Reply via email to