Because it has already been discussed, I might as well throw in my two
cents.
Whatever direction commons decides to take, it's worth acknowledging
that more than a few popular Apache projects moved to
org.apache.whatever.* without relocating their previous releases. They
broke with the Maven 1 conventions and released new versions under the
naming conventions for Maven 2. Because developers must modify their POM
to update the version number anyway, editing the groupId is a trivial
additive.
Paul
Henri Yandell wrote:
On 7/9/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 7/9/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> For development of new releases, should the commons-* folders be
forgone
> and use org.apache.commons now?
Check the list archives for some past discussion... it has to be
handled carefully with old releases "relocated" in the central
repository, or downstream users will be adversely affected.
Nabble turns up a few relevant posts:
http://www.nabble.com/forum/Search.jtp?forum=317&local=y&query=commons+maven+groupid
Yeah, my view is that Maven need a better system :) I keep meaning to
dig into the code of how to do such a thing.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
