I think the general consensus is - don't do this. Just don't.
(that "move" is moving from one repository to another, not moving groupIds btw - my bad - but I coulda sworn they do offer a move feature) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Anders Hammar Sent: Tuesday, August 24, 2010 4:07 PM To: Maven Users List Subject: Re: Correcting a groupID I'm wondering how they handle the pgp signatures. If the groupId changes, the pom changes, and then the signature won't be correct. I would never mess with old releases. /Anders On Tue, Aug 24, 2010 at 20:27, EJ Ciramella <[email protected]>wrote: > 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:[email protected]] > 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 <[email protected]> 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:[email protected]] > > 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > 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: [email protected] > For additional commands, e-mail: [email protected] > > > 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: [email protected] > For additional commands, e-mail: [email protected] > > 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: [email protected] For additional commands, e-mail: [email protected]
