+1 But if they don't share the same repository id, if you happened to have both snapshots repos in your POM file, the newer snapshot will be the one to be picked, no?. So as long as you add the new snapshot repository with a new id you should be safe. Of couse, to replace the old one would be recommended...
Cheers, Bruno On 24 August 2010 10:18, Jakob Korherr <[email protected]> wrote: > Hi Mark, > > +1 > > This means that we have to remove all snapshot-repo entries from our poms, > right? > > Regards, > Jakob > > 2010/8/24 Mark Struberg <[email protected]> > > Hi folks! >> >> With the new apache parent, we also got a new snapshots repository. We now >> face >> the problem to have 2 apache-snapshots repositories which will not work >> without >> overriding the maven metainfo of each other. >> >> To work around those weird problems I usually have the following entry in >> my >> ~/.m2/settings.xml: >> >> <mirrors> >> <mirror> >> <id>new.apache.snapshots</id> >> <name>new apache snapshots repository. We need this to skip the old >> ones</name> >> <url>http://repository.apache.org/snapshots</url> >> <mirrorOf>apache.snapshots</mirrorOf> >> </mirror> >> </mirrors> >> >> We should move over to the new snapshost-repo and then drop the old one >> completely. This will work as long as no pom is referenced which >> virulently >> pulls in the old snapshots repo. >> >> LieGrue, >> strub >> >> >> >> > > > -- > Jakob Korherr > > blog: http://www.jakobk.com > twitter: http://twitter.com/jakobkorherr > work: http://www.irian.at >
