You're using <version>[1.2.2]</version> and Maven is reaching out for that dependencies' pom even though its installed locally? I ask because this is not my experience with the tool.
I can force Maven to check Central with "mvn -U" but without -U my build proceeds using dependencies (with versions as specified) only from my local repo. Wayne On 4/13/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > even for some things with version numbers listen in our pom, maven still > reaches out for that artifacts pom. > > > -----Original Message----- > From: Barrie Treloar [mailto:[EMAIL PROTECTED] > Sent: Thu 4/13/2006 1:00 AM > To: Maven Users List > Subject: Re: use of proxies > > On 4/13/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > All I'm attempting to do is prevent builds from going to the maven > > repository. I have set up one machine (build.corp.upromise.com) that has > > everything from my .m2/repository directory (I copied it there). > > The first question is: why? > > Maven manages your build dependencies. Use version numbers in your pom > dependencies to lock down what should be used instead of restricting > access to central. > > --------------------------------------------------------------------- > 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] > >
