commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Wiedmann <jochen.wiedm...@gmail.com>
Subject Re: [NET] Move to o.a.c Maven groupId
Date Mon, 16 Aug 2010 13:22:55 GMT
The problem is this: Commons libraries are more than likely to be used
by multiple dependencies. That's no problem for Maven, if they have
the same group and artifact Id. Maven eliminates the predecessor from
the dependency list. That won't work if the group Id has changes.

Jochen


2010/8/16 Rafał Krupiński <r.krupinski@gmail.com>:
> On Mon, Aug 16, 2010 at 1:41 PM, Jochen Wiedmann
> <jochen.wiedmann@gmail.com> wrote:
>> The idea is vice versa: Do not change the groupId, unless you are
>> considering changes as serious as changing the package name.
>
> I don't see why.
> Domain based groupIds are standard now, they are easier to find in IDE
> tools and I hear maven people handle repository updates automatically,
> as opposed to non-domain-based groupIds which have to be handled
> manually.
>
> --
> Pozdrawiam / Best Regards
> Rafal Krupinski
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>



-- 
I Am What I Am And That's All What I Yam (Popeye)

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


Mime
View raw message