dev@glassfish.java.net

Re: please approve top-level pom.xml change

From: Snjezana Sevo-Zenzerovic <Snjezana.Sevo-Zenzerovic_at_Sun.COM>
Date: Mon, 03 Aug 2009 14:54:35 -0700

Well, saying that something is coming from packager/external also
doesn't say much about true source of the content since those modules
take some external artifact (hence the group name) and repackage it in
some way to fit GlassFish needs (by enabling OSGi, or tweaking file
layout, or something similar)...

ArtifactID eventually becomes an issue if it starts to clash with
another artifactID installed in the same location. Once the jar names
are stripped of the version, one of them will get clobbered...

Thanks,

Snjezana

Lloyd Chambers wrote:

> Ken and I discussed this today.
>
> The artifactId is actually a problem, it's too similar to
> "management-api" eg JSR 77.
>
> So we should change the artifactId. I'm looking into this.
>
> Why is packager using org.glassfish.external?
>
> Lloyd
>
> On Aug 3, 2009, at 12:45 PM, Jane Young wrote:
>
>> The version is fine. The groupId is confusing since in
>> v3/packager/external, the artifacts there all have the groupId
>> "org.glassfish.external" so I thought this module is in this
>> location. Can we name the groupId "org.glassfish.gmbal" (same as
>> the gmbal artifacts)? The artifactId is fine as "management-api".
>>
>> Jane
>>
>>
>> Ken Cavanaugh wrote:
>>
>>> Lloyd Chambers wrote:
>>>
>>>> Jane,
>>>>
>>>> management-api.jar is Ken Cavanaugh's project, part of Gmbal, over
>>>> on kenai.
>>>
>>> It's really not my project (or at least the code is not mine), I
>>> just manage it for primarily Prashanth and Lloyd.
>>> It's part of the Gmbal project on Kenai, but management-api is in a
>>> separate mercurial
>>> repository. Currently the URLs for the workspaces are:
>>>
>>> * gmbal: https://kenai.com/hg/gmbal~master
>>> * management-api: https://kenai.com/hg/gmbal~gf_common
>>>
>>> By the way, is the version named glassfish-management-api.version to
>>> avoid confusion with the
>>> other management-api artifact? If so, we really should consider
>>> cleaning up the names.
>>>
>>> Ken.
>>>
>>>>
>>>> Lloyd
>>>>
>>>> On Aug 3, 2009, at 12:11 PM, Jane Young wrote:
>>>>
>>>>> Approved.
>>>>> BTW: where is management-api artifact getting built?
>>>>>
>>>>> Lloyd Chambers wrote:
>>>>>
>>>>>> This change revs management-api.jar to version b004.
>>>>>>
>>>>>>
>>>>>> llcMP:code llc$ svn diff pom.xml
>>>>>> Index: pom.xml
>>>>>> ===================================================================
>>>>>> --- pom.xml (revision 30046)
>>>>>> +++ pom.xml (working copy)
>>>>>> @@ -160,7 +160,7 @@
>>>>>> <jbi.version>1.0</jbi.version>
>>>>>> <wsdl4j.version>1.6.2</wsdl4j.version>
>>>>>> <gmbal.version>3.0.0-b009</gmbal.version>
>>>>>> -
>>>>>> <glassfish-management-api.version>3.0.0-b003</glassfish-management-api.version>
>>>>>> +
>>>>>> <glassfish-management-api.version>3.0.0-b004</glassfish-management-api.version>
>>>>>> </properties>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Lloyd Chambers
>>>>>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>>>>>> GlassFish Team
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> Lloyd Chambers
>>>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>>>> GlassFish Team
>>>>
>>>>
>>>>
>>>
>>
>
> Lloyd Chambers
> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
> GlassFish Team
>
>
>