Wendy Smoak wrote:
On 11/24/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
I presume that this is being done as part of some Commons-wide policy
change? If so, it's incumbent on us to clearly document the impact of
this
change on downstream users, because it is going to be pretty disruptive
until all downstream users have rev'd their POMs to reflect the new
versions.
It shouldn't be disruptive at all if the artifacts are properly
"relocated" in the Maven repo.
ISTR Dennis Lundberg was working on it.
Yes, I was. See [1] and [2] for a bit of background. Unfortunately I ran
out of steam. There just didn't seem to be any real commitment to the
idea from the community. Sorry to have left things in a
not-quite-finished state.
I did manage to write some documentation [3] on how to manage the
"relocation" that Wendy speaks of.
My stand on this at the moment is to await the transition to Maven 2 as
the main build platform for Commons. When we start using Maven 2 to
build our binary releases, they should at the same time change the
groupId. However, if someone feels that we should go ahead with the
migration using Maven 1 I'll help in any way I can.
[1]http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/200605.mbox/[EMAIL
PROTECTED]
[2]http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/200605.mbox/[EMAIL
PROTECTED]
[3]http://maven.apache.org/guides/mini/guide-relocation.html
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
