On 24 August 2010 08:34, Baptiste MATHUS <[email protected]> wrote: > 2010/8/23 sebb <[email protected]> > >> 2010/8/23 Arnaud Héritier <[email protected]>: >> > I think it could help you : >> > http://maven.apache.org/guides/mini/guide-relocation.html >> >> Thanks - but it does not really cover the Apache case where a shared >> repo is used. > > > Sorry. I don't know Apache infra well, but I don't understand why the > relocation won't suit your needs. Could you clarify? > > The principle is simple : > * change whatever you want in your pom groupId/artifactId > * publish both the resulting new artifact, and only a pom in the old place, > so that maven will find it, display a warning and continue gracefully. > * Do that for two or three releases for examples, to give users time to > update > * Finally, continue releasing on the new place, and no more in the old one.
That makes sense, however as I read it one also has to do the following: # Copy all foo-related files from /bar/foo/ in your Maven 2 repository to a temporary location. # Change the groupId to org.bar in all foo-related pom files in the temporary location. # Copy all files from the temporary location to /org/bar/foo/ in your Maven 2 repository. # Create a minimal Maven 2 pom file for every old release of foo in your Maven 2 repository. etc. before the steps that you suggest. This would be difficult / tedious with Nexus, as it would mean registering the old groupId as well as the new one. Are those steps really necessary? If not, why are they documented? > Cheers > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
