> I think the general consensus is - don't do this. > > Just don't.
I think its OK for a project to "move" groupIds and then use that new groupId for all future releases. But I don't think it should ever be OK for a project to "move" groupIds for past releases -- that breaks the "don't ever change stuff once released" rule Leave old stuff where it is, put relocation poms in the old place pointing to the new stuff for a while, and put the new stuff directly in the new place. This is how groupId should be "corrected." Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
