No not the Windows Resigstry. The local Maven Repository, by default located at ~/.m2/repository
> -----Original Message----- > From: Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) > [mailto:[EMAIL PROTECTED] > Sent: Saturday, 7 October 2006 8:10 AM > To: 'Maven Users List' > Subject: RE: [M2] Overriding the Central Repository not working > > > Peter, what "local registry" do you speak of? Do you mean > the Windows registry? The reason I ask is I'm about to try > the same thing, but I'm using Linux. > > Thanks, > --Marilyn > > -----Original Message----- > From: Peter Anning [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 05, 2006 11:34 PM > To: Maven Users List > Subject: RE: [M2] Overriding the Central Repository not working > > Anyway Arnaud Bailly was right I have solved my problem by > creating a Bash script moving all the > maven-metadata-central.xml to maven-metdata.xml regenerating > the sha1 files and delete al unwanted maven-metadata-*.xml > files in the copy of the local registry. Also my plugins that > were Snapshots have been released and deployed to the local > newtwork repository. > > Now running a mirror of Central as the override on the local > network and all is happy > > Cheers > > Peter > > "Talking to yourself may be the first sign of maddnes, but it > is the only way to get sensible answers" > > > > -----Original Message----- > > > From: Arnaud Bailly [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, 4 October 2006 5:43 PM > > > To: Maven Users List > > > Subject: Re: [M2] Overriding the Central Repository not working > > > > > > > > > "Peter Anning" <[EMAIL PROTECTED]> writes: > > > > > > > Hi, > > > > > > > > > > Hello, > > > > > > > I do a build with a vanilla settings.xml add any stuff I > > need to my > > > > local repository by hand. Then make a network copy of the local > > > > repository delete my local repository and then my > troubles start. > > > > > > > > > > This won't work, AFAIK. There is metadata information > stored in the > > > repository which identifies it (the information) as local > or tied to > > > a specific remote repo. This means, I think, that you > cannot simply > > > copy > > > (local) repositories around and hope it will work. You need to > > > deploy files or use a proxy as Wayne Fay advised you. > > > > > > I have been bitten in the past by this in relation with custom > > > plugins. > > > > > > HTH > > > -- > > > OQube < software engineering \ génie logiciel > Arnaud > Bailly, Dr. > > > \web> http://www.oqube.com > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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]
