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. In another life, I casually agreed we should change the groupId of an artifact and all hell broke loose... -----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.
