Also, I'm not convinced it's a nexus thing. I've removed (completely) the local storage for repo1 (where this artifact is proxied from).
I think it has to do with this dependency chain: [DEBUG] com.sun.jersey.contribs:jersey-spring:jar:1.4:compile [DEBUG] org.springframework:spring-web:jar:2.5.6.SEC03:compile Are you having issues with that as well? On Tue, Sep 27, 2011 at 2:37 PM, Maven User <maven.2.u...@gmail.com> wrote: > Is there an easy way to see from the command line which repository an > artifact is being resolved to/from? > > > On Thu, Sep 22, 2011 at 11:03 PM, Wayne Fay <wayne...@gmail.com> wrote: > >> > Downloaded: http:// >> <SERVER>/nexus/content/groups/public/org/springframework/spring-web/maven-metadata.xml >> > >> > Is there a known issue with this particular artifact within repo1? Any >> > suggestions on how to fix this? >> >> I have no problems accessing this file on repo1 [1]. I expect this >> must be happening as a result of something going on in your Nexus >> instance. Why don't you ask on their user list? Perhaps there's a log >> you should check for more details etc. >> >> [1] >> http://repo1.maven.org/maven2/org/springframework/spring-web/maven-metadata.xml >> >> Wayne >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
