On Thu, Aug 28, 2008 at 9:56 PM, simon <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2008-08-27 at 15:28 +0200, Niklas Gustavsson wrote:
>> Hi
>>
>> commons-net still uses "commons-net" as the groupId. Other commons
>> components (including the parent POM) seems to have changed to
>> org.apache.commons. Is there any reason for not making the same change
>> for net?
>
> Note that I'm not speaking for commons-net here, just commenting in
> general.
>
> Very few commons components have changed their groupId, AFAIK.
>
> It is generally agreed that a groupId of "org.apache.commons.*" would be
> better. However when changing the groupId it is necessary to also
> correctly deploy a "redirect" pom to tell maven that the groupId has
> been changed; failing to do this can result in an app getting two copies
> of the same library in the classpath because Maven does not know that
> the two different groupIds are actually equivalent.
>
> Deploying this "redirect" pom must be done at the same time as a version
> release.
>
> And because the central repo artifacts should never be modified, the
> redirect pom had better be correct the first time, or things get
> embarrassing.
>
> So AFAIK projects have generally avoided making the change simply
> because of worry about getting the redirect pom wrong, plus the lack of
> any major benefit to compensate for the extra work it involves.
>
> Changing the groupId of a parent pom is much easier actually; no
> redirect pom is needed because parent poms don't have "version
> resolution" going on, where 1.0 or 1.1 or 2.3 or whatever can be chosen
> depending on transient dependencies. Instead for a parent pom the
> version to use has to be explicitly specified.

Some previous threads on this are here:

http://markmail.org/message/tky6c734r2dia2gd
http://markmail.org/message/gov633sq5mgzjnkp
http://markmail.org/message/rl4cueaxa7q75wgf
http://markmail.org/message/wdrgfppjrppbofqc

Niall

> Regards,
> Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to