Additionally, when I was done crying myself to sleep over this failure, I went in search of a repo manager that allowed an easy way to do this in the future:
http://wiki.jfrog.org/confluence/display/RTF/Moving+Artifacts But I'm sticking with Nexus until it bites me... -----Original Message----- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, August 24, 2010 2:08 PM To: Maven Users List Subject: Re: Correcting a groupID On 24 August 2010 18:44, EJ Ciramella <ecirame...@casenetinc.com> wrote: > Yeah, I know - hate to cross-pollinate here but the Nexus bible states the > repo is for deposits only. > > Essentially backing up the "just change NEW snapshots/releases, leave the old > ones where they are" sentiment. OK > In another life, I casually agreed we should change the groupId of an > artifact and all hell broke loose... Did you use relocation POMs? What were the exact problems? Could they have been avoided, and if so, how? > > > -----Original Message----- > From: Wayne Fay [mailto:wayne...@gmail.com] > Sent: Tuesday, August 24, 2010 11:00 AM > To: Maven Users List > Subject: Re: Correcting a groupID > >> The guide to relocation: >> >> http://maven.apache.org/guides/mini/guide-relocation.html > > Hmmmmmmm I really don't agree with this approach, and don't believe it > would pass muster today. This documentation is most likely old. > > Today's mantra is "artifacts don't change". This includes poms and > jars etc. I believe the correct approach today would be to put > relocation poms in the old groupId for the new artifact for any new > artifacts for a few releases, while putting the artifacts themselves > in the new groupId, and then stop putting the relocation poms in > completely after some period of time. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > CONFIDENTIALITY NOTICE: This e-mail and the information transmitted within > including any attachments is only for the recipient(s) to which it is > intended and may contain confidential and/or privileged material. Any review, > retransmission, dissemination or other use of; or taking of any action in > reliance upon this information by persons or entities other than the intended > recipient is prohibited. If you received this in error, please send the > e-mail back by replying to the sender and permanently delete the entire > message and its attachments from all computers and network systems involved > in its receipt. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org CONFIDENTIALITY NOTICE: This e-mail and the information transmitted within including any attachments is only for the recipient(s) to which it is intended and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of; or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please send the e-mail back by replying to the sender and permanently delete the entire message and its attachments from all computers and network systems involved in its receipt. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
