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
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
The core issue is one of transitive dependencies clashes.
For example, I had a problem the other day with the antrun plugin
which depends on ant.ant-1.6.5, and we had a dependency of ant-trax
(1.7.0), which depends on org.apache.ant.ant-1.7.0. Those aren't the
same project, so Maven couldn't
Good points. I've been through that very same problem many times. I
guess I am just used to excluding the old names. Yeah, it's a bit of a
troublemaker, but I'd rather have a correct name. In any case, perhaps
this name-game will gain traction once Maven adds capabilities to
provide aliases.
For development of new releases, should the commons-* folders be forgone
and use org.apache.commons now?
Thanks,
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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,
