Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <D4746707-E9F7-46FF-9C7D-154C2AC4EE95@apache.org>
References: <CAOGo0VbYLsVF5DO9nBStdUhCYzamY8UgUiGkHVOMiOADqxEk6Q@mail.gmail.com>
 <D4746707-E9F7-46FF-9C7D-154C2AC4EE95@apache.org>
From: sebb <sebbaz@gmail.com>
Date: Fri, 21 Apr 2017 17:39:05 +0100
Message-ID: <CAOGo0VabXXJZiuO-Nwbt3SN8qwuh5_PPTdYeF4yQN_ydHk9PpQ@mail.gmail.com>
Subject: Re: [ALL] explicit Maven groupId in component POMs
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 21 Apr 2017 16:39:23 -0000

On 21 April 2017 at 16:54, Benedikt Ritter <britter@apache.org> wrote:
>
>> Am 21.04.2017 um 15:12 schrieb sebb <sebbaz@gmail.com>:
>>
>> Commons components use two different styles of groupId:
>>
>> commons-<component> - used by some original components (e.g. IO, NET)
>> org.apache.commons - newer style, used by most components
>>
>> Since Commons Parent uses the latter, and the groupId is inherited, in
>> theory a component using the new groupId does not need to specify it.
>>
>> However, I think that is unwise, as it's not clear whether the
>> omission is deliberate or accidental.
>> Also the parent could potentially be changed to one with a different gro=
upId.
>>
>> Far better to specify the groupId explicitly rather than relying on an
>> inherited default.
>>
>> Agreed?
>
> -1: it=E2=80=99s redundant and unnecessary.

Strictly speaking, yes.

But the problem is that it would be very easy to change the parent gid
and assume that everything is still OK.

Especially with Commons which has a mixture of groupIds, I think it's
important to explicitly state the intended groupId for each component.

>>
>> S.
>> P.S. Note that changing the groupId can only be done if the package
>> name is also changed, see
>> https://wiki.apache.org/commons/MavenAndClasspath
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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