K
On Apr 21, 2017 6:21 AM, "Emmanuel Bourg" wrote:
Le 21/04/2017 à 15:12, sebb a écrit :
> Agreed?
I don't mind, but IntelliJ will highlight the groupId and suggest to
remove it :)
Same in Eclipse. POMs are big enough as it is, I prefer to keep the config
by exception going, but that's just
Am 21.04.2017 um 15:21 schrieb Emmanuel Bourg:
I don't mind, but IntelliJ will highlight the groupId and suggest to
remove it :)
Eclipse also warns that the groupId duplicates the parent groupId.
I prefer not to duplicate the parent groupId.
Cheers,
Pascal
Le 21/04/2017 à 18:39, sebb a écrit :
> But the problem is that it would be very easy to change the parent gid
> and assume that everything is still OK.
But why would we change the parent groupId? It hasn't changed since its
first release 10 years ago and I don't see the need for a new name.
Emm
On 21 April 2017 at 16:54, Benedikt Ritter wrote:
>
>> Am 21.04.2017 um 15:12 schrieb sebb :
>>
>> Commons components use two different styles of groupId:
>>
>> commons- - used by some original components (e.g. IO, NET)
>> org.apache.commons - newer style, used by most components
>>
>> Since Commo
> Am 21.04.2017 um 15:12 schrieb sebb :
>
> Commons components use two different styles of groupId:
>
> commons- - 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,
Le 21/04/2017 à 15:12, sebb a écrit :
> Agreed?
I don't mind, but IntelliJ will highlight the groupId and suggest to
remove it :)
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional comma
Commons components use two different styles of groupId:
commons- - 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 nee
