commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: [configuration] Artifact name
Date Tue, 23 Jun 2009 00:32:59 GMT
Is configuration2 binary incompatible with configuration (1)?  If it
is, then you should consider changing the package name and using:

artifactId: commons-configuration2
groupId: org.apache.commons

This would be for consistency's sake.

On Mon, Jun 22, 2009 at 8:05 PM, Ralph Goers<ralph.goers@dslextreme.com> wrote:
> configuration2 should use groupId org.apache.commons and an artifactId of
> commons-configuration. I am not going to worry about configuration3 - we are
> still a long way off from completing configuration2.
>
> Ralph
>
> On Jun 22, 2009, at 3:22 PM, Emmanuel Bourg wrote:
>
>> Jörg Schaible a écrit :
>>
>>> Simply because the groupId change is a one time action only and will not
>>> scale for configuration3 ;-)
>>
>> Bah, when Commons Configuration started, Maven didn't have groupIds, there
>> was a unique id. That was 5 years ago. Configuration 2 is far from finished,
>> Configuration 3 will certainly not happen before 5 more years. By that time
>> the technical constraints will probably change, and the issue will be solved
>> differently.
>>
>> Emmanuel Bourg
>>
>> ---------------------------------------------------------------------
>> 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


Mime
View raw message