Second try - having had it explained to me on #maven why relocating is important [so commons-lang:commons-lang 2.1 and org.apache.commons:commons-lang 3.0 are considered the same and a transitive clash can be recognized].
So, second suggestion: We declare a point after which we won't do any more m1 releases. We'll move wholesale over to m2. On that day (or as near as we can), we run a script on all commons-*/ to do the relocation for all of them ( http://maven.apache.org/guides/mini/guide-relocation.html ). I know I'm clueless - so please change this to whatever the clueful one is. I think it's time for us to drop m1 and move to m2. Hen On 2/12/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
This has come up a number of times and I'm not sure if the last time saw an agreement. My understanding is that we want to move to org.apache.commons. We've dabbled with the idea of relocating, but it sounds like that is more trouble than it's worth. Are we now of the view that: 1) Maven-1 builds stay as commons-foo 2) Maven-2 builds all set the groupId to org.apache.commons ?? Hen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
