Hmm - digging slightly deeper, we have a direct dependency on spring-web 3.0.5.RELEASE.
But that is resolving to org.springframework:spring-web:jar:2.5.6.SEC03:compile I'm guessing this is a transitive dependency, but I don't see it with dependency:tree. On Tue, Sep 27, 2011 at 7:59 PM, Mark Derricutt <[email protected]> wrote: > Are you by any chance using version ranges in any of your poms - that tends > to cause maven to repeatedly download the metadata when checking for newer > versions to satisfy your ranges. > > > > On 28/09/2011, at 7:37 AM, Maven User 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 <[email protected]> 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: [email protected] > >> For additional commands, e-mail: [email protected] > >
