> # 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.

That is definitely NOT the way to handle it. Once released, artifacts
(including pom files) must not change. Why do you think this
should/must be done?? Is it merely a poor assumption on your part, or
were you told this or read it somewhere?

You simply leave the old files where they are. And slowly migrate to
the new groupId, just as you were previously told, by using the
relocation poms for new releases in the old groupId and then actually
pushing the new artifacts and poms to the new groupId.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to