Todd, The artifact that Maven fails to download is not the one that's different between Maven Central and java.net. Rather, it's a parent pom of the original artifact that differs. It all starts with the com.sun.jersey.contribs:jersey-spring:1.1.4:jar artifact, which depends on org.springframework:spring:[2.5.2) (maybe the use of a non-fixed version in the dependency is related somehow?):
com.sun.jersey.contribs:jersey-spring:1.1.4:jar has a parent of com.sun.jersey.contribs:jersey-contribs:1.1.4:pom which has a parent of com.sun.jersey:jersey-project:1.1.4:pom It's the final artifact (com.sun.jersey:jersey-project:1.1.4:pom) that differs on Maven Central and java.net and it's the dependent artifact (org.springframework:spring:jar:2.5.6) that Maven fails to download. Earlier in this thread, we discussed raising a defect against Maven Central or java.net, but I'm not knowledgeable enough about the situation to know which artifact is the correct one. Therefore, I'm not comfortable raising a defect against either repository. Kyle -----Original Message----- From: Thiessen, Todd (Todd) [mailto:[email protected]] Sent: Friday, August 19, 2011 4:21 PM To: Maven Users List Subject: RE: com.sun.jersey:jersey-project:1.1.4:pom artifact differs on Maven Central and java.net I realize that not having the repo section defined "shouldn't" be causing a problem (we have been scratching our heads over that one for a couple of days). But the two poms that Kyle referenced have the same GAV, both released, yet have different contents. I thought that was a big no no in the maven world. Should a Jira be raised against Maven central to rectify the difference in released artifacts? > -----Original Message----- > From: Brian Fox [mailto:[email protected]] > Sent: Friday, August 19, 2011 4:02 PM > To: Maven Users List > Subject: Re: com.sun.jersey:jersey-project:1.1.4:pom artifact differs > on Maven Central and java.net > > This is even stranger. That jar is/has been in central: > http://search.maven.org/#artifactdetails|org.springframework|spring|2.5 > .6|jar > > The changes to the jersey pom shouldn't have affected this at all. > > On Fri, Aug 19, 2011 at 1:26 PM, Blaney, Kyle (Kyle) > <[email protected]> wrote: > > Brian, > > > > The following build failure occurs when a project specifies a direct > dependency on com.sun.jersey.contribs:jersey-spring:1.1.4:jar: > > > > [ERROR] BUILD ERROR > > [INFO] -------------------------------------------------------------- > ---------- > > [INFO] Failed to resolve artifact. > > > > Missing: > > ---------- > > 1) org.springframework:spring:jar:2.5.6 > > > > Try downloading the file manually from the project website. > > > > Then, install it using the command: > > mvn install:install-file -DgroupId=org.springframework - > DartifactId=spring > > -Dversion=2.5.6 -Dpackaging=jar -Dfile=/path/to/file > > > > Alternatively, if you host your own repository you can deploy the > file there: > > > > mvn deploy:deploy-file -DgroupId=org.springframework - > DartifactId=spring - > > Dversion=2.5.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] - > DrepositoryId=[ > > id] > > > > Path to dependency: > > 1) com.avaya.kblaney:test-aie:jar:3.0.0-SNAPSHOT > > 2) com.sun.jersey.contribs:jersey-spring:jar:1.1.4 > > 3) org.springframework:spring:jar:2.5.6 > > > > ---------- > > 1 required artifact is missing. > > > > for artifact: > > com.avaya.kblaney:test-aie:jar:3.0.0-SNAPSHOT > > > > from the specified remote repositories: > > central (http://nexus.forge.avaya.com/content/groups/public), > > ace_special > (http://nexus.forge.avaya.com/content/repositories/ace_special) > > --------------------------------------- > > > > Note that the com.springframework:spring artifact does in fact exist > in our "central" repository. I called the build error strange because > the failure only occurs with certain combinations of repositories > defined in pom.xml and mirrors defined in settings.xml. I will provide > the pom.xml and settings.xml if necessary. > > > > So far, we have discovered the following workarounds: > > > > 1. In pom.xml, specify a direct dependency on > org.springframework:spring:2.5.6 (even though it's not really a direct > dependency; rather, it's a transitive dependency of > com.sun.jersey.contribs:jersey-spring:1.1.4). I don't understand why > changing the dependency to a direct one gets Maven to download it from > our central repo, but it does. > > > > 2. In pom.xml, specify our Nexus java.net copy as the first > repository and in settings.xml, specify our Nexus java.net copy as the > first mirror. > > > > Kyle > > > > > > -----Original Message----- > > From: Brian Fox [mailto:[email protected]] > > Sent: Friday, August 19, 2011 12:33 PM > > To: Maven Users List > > Subject: Re: com.sun.jersey:jersey-project:1.1.4:pom artifact differs > on Maven Central and java.net > > > > 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) > <[email protected]> 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
