[net] GroupId from commons-net

[Niklas Gustavsson <ni...@protocol7.com>]

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?

/niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [net] GroupId from commons-net

[Niklas Gustavsson <ni...@protocol7.com>]

On Thu, Aug 28, 2008 at 10:56 PM, simon <sk...@apache.org> wrote:
> 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.

Would this also be applicable in the case of commons-net 2.0 which
breaks backwards compatibility and thus is not a automatic replacement
for the existing commons-net releases? A user ending up with both
commons-net-1.4 and commons-net-2.0 in her classpath would surely be
confused, but that's also true if she gets 1.4 replaced by 2.0 behind
the scenes.

> 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.

Yeah, I sure don't want to get into that mess :-)

/niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [net] GroupId from commons-net

[Niall Pemberton <ni...@gmail.com>]

On Thu, Aug 28, 2008 at 9:56 PM, simon <sk...@apache.org> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [net] GroupId from commons-net

[simon <sk...@apache.org>]

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.

Regards,
Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org