You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stefan Bodewig <bo...@apache.org> on 2011/08/12 08:41:34 UTC
[jcs] groupId
Hi,
while looking through the Gump setup for JCS I realized the artifactId
inside the POM had been changed to commons-jcs while the groupId still
is org.apache.jcs. Does it make sense to keep the old groupId when
you change the artifactId anyway?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jcs] groupId
Posted by sebb <se...@gmail.com>.
On 14 August 2011 10:38, Thomas Vandahl <tv...@apache.org> wrote:
> On 12.08.11 08:41, Stefan Bodewig wrote:
>> Hi,
>>
>> while looking through the Gump setup for JCS I realized the artifactId
>> inside the POM had been changed to commons-jcs while the groupId still
>> is org.apache.jcs. Does it make sense to keep the old groupId when
>> you change the artifactId anyway?
>
> I just thought it was a good idea and it wouldn't do much harm. I agree
> that it is probably better to keep the previous combination for now. I
> will revert the change.
Thanks.
Unfortunately changing the group id without a corresponding package
change can cause lots of problems.
Maven treats it as a different artifact, but the classloader does not.
Package id and Maven group:artifact ids must be changed together.
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> 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
Re: [jcs] groupId
Posted by Thomas Vandahl <tv...@apache.org>.
On 12.08.11 08:41, Stefan Bodewig wrote:
> Hi,
>
> while looking through the Gump setup for JCS I realized the artifactId
> inside the POM had been changed to commons-jcs while the groupId still
> is org.apache.jcs. Does it make sense to keep the old groupId when
> you change the artifactId anyway?
I just thought it was a good idea and it wouldn't do much harm. I agree
that it is probably better to keep the previous combination for now. I
will revert the change.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jcs] groupId
Posted by Jörg Schaible <jo...@scalaris.com>.
Emmanuel Bourg wrote:
> IMHO unless the main package name has to change due to binary
> incompatibilities in the new version I would stick to the original
> groupId/artifactId (ie org.apache.jcs/jcs).
+1
otherwise Stefan is right and we can adjust the groupId also.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jcs] groupId
Posted by sebb <se...@gmail.com>.
On 13 August 2011 21:22, James Carman <ja...@carmanconsulting.com> wrote:
> If you change stuff around, you need to change the package name(s),
> right? Otherwise, you could have collisions on the classpath.
Yes, but then everyone using the code will need to edit and recompile.
So best to keep binary compatibility if at all possible.
> On Fri, Aug 12, 2011 at 4:26 AM, Jörg Schaible
> <jo...@scalaris.com> wrote:
>> Stefan Bodewig wrote:
>>
>>> On 2011-08-12, Emmanuel Bourg wrote:
>>>
>>>> IMHO unless the main package name has to change due to binary
>>>> incompatibilities in the new version I would stick to the original
>>>> groupId/artifactId (ie org.apache.jcs/jcs).
>>>
>>> I agree with you. But if jcs changes the artifactId (which has happened
>>> in trunk) there is no point in keeping the groupId or is there?
>>
>> Right. Different G:A means different project and neither Maven nor any other
>> dependency managing system will match those properly (even in case of this
>> fruitless relocation stuff) calculating versions.
>>
>> - Jörg
>>
>>
>> ---------------------------------------------------------------------
>> 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
Re: [jcs] groupId
Posted by James Carman <ja...@carmanconsulting.com>.
If you change stuff around, you need to change the package name(s),
right? Otherwise, you could have collisions on the classpath.
On Fri, Aug 12, 2011 at 4:26 AM, Jörg Schaible
<jo...@scalaris.com> wrote:
> Stefan Bodewig wrote:
>
>> On 2011-08-12, Emmanuel Bourg wrote:
>>
>>> IMHO unless the main package name has to change due to binary
>>> incompatibilities in the new version I would stick to the original
>>> groupId/artifactId (ie org.apache.jcs/jcs).
>>
>> I agree with you. But if jcs changes the artifactId (which has happened
>> in trunk) there is no point in keeping the groupId or is there?
>
> Right. Different G:A means different project and neither Maven nor any other
> dependency managing system will match those properly (even in case of this
> fruitless relocation stuff) calculating versions.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> 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
Re: [jcs] groupId
Posted by Jörg Schaible <jo...@scalaris.com>.
Stefan Bodewig wrote:
> On 2011-08-12, Emmanuel Bourg wrote:
>
>> IMHO unless the main package name has to change due to binary
>> incompatibilities in the new version I would stick to the original
>> groupId/artifactId (ie org.apache.jcs/jcs).
>
> I agree with you. But if jcs changes the artifactId (which has happened
> in trunk) there is no point in keeping the groupId or is there?
Right. Different G:A means different project and neither Maven nor any other
dependency managing system will match those properly (even in case of this
fruitless relocation stuff) calculating versions.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jcs] groupId
Posted by Stefan Bodewig <bo...@apache.org>.
On 2011-08-12, Emmanuel Bourg wrote:
> IMHO unless the main package name has to change due to binary
> incompatibilities in the new version I would stick to the original
> groupId/artifactId (ie org.apache.jcs/jcs).
I agree with you. But if jcs changes the artifactId (which has happened
in trunk) there is no point in keeping the groupId or is there?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jcs] groupId
Posted by sebb <se...@gmail.com>.
On 12 August 2011 08:14, Emmanuel Bourg <eb...@apache.org> wrote:
> IMHO unless the main package name has to change due to binary
> incompatibilities in the new version I would stick to the original
> groupId/artifactId (ie org.apache.jcs/jcs).
+1, otherwise users will be forced to edit and recompile - such
changes effectively make it a new component.
> Emmanuel Bourg
>
>
> Le 12/08/2011 08:41, Stefan Bodewig a écrit :
>>
>> Hi,
>>
>> while looking through the Gump setup for JCS I realized the artifactId
>> inside the POM had been changed to commons-jcs while the groupId still
>> is org.apache.jcs. Does it make sense to keep the old groupId when
>> you change the artifactId anyway?
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> 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
Re: [jcs] groupId
Posted by Emmanuel Bourg <eb...@apache.org>.
IMHO unless the main package name has to change due to binary
incompatibilities in the new version I would stick to the original
groupId/artifactId (ie org.apache.jcs/jcs).
Emmanuel Bourg
Le 12/08/2011 08:41, Stefan Bodewig a écrit :
> Hi,
>
> while looking through the Gump setup for JCS I realized the artifactId
> inside the POM had been changed to commons-jcs while the groupId still
> is org.apache.jcs. Does it make sense to keep the old groupId when
> you change the artifactId anyway?
>
> Stefan
>
> ---------------------------------------------------------------------
> 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