dev@glassfish.java.net

Re: GlassFish parent pom changes

From: Tang Yong <tangyong_at_cn.fujitsu.com>
Date: Tue, 18 Sep 2012 21:05:10 +0900

Hi Romain

   I have confirmed that the problem has been fixed based on the newest
trunk.

   Thanks for the fix!

-Tang

Romain Grecourt wrote:
> I've checked in the fix.
> Please re-open if needed.
>
> Thanks!
> Romain
>
> On 9/14/12 11:24 AM, Romain Grecourt wrote:
>> Hi Tang,
>>
>> Thank you for identify this issue.
>> I will verify the fix and check it in.
>>
>> Thanks!
>> Romain
>>
>> On 9/14/12 7:48 AM, Tang Yong wrote:
>>> Hi Romain, GUI)Anissa
>>>
>>> Since the change of poms between nucleus and appserver, I have
>>> found a problem related to this change. Pl. see
>>> http://java.net/jira/browse/GLASSFISH-19074
>>>
>>> wish that the change does not cause new regressions.
>>>
>>> Thanks!
>>> --Tang
>>>
>>> Sahoo wrote:
>>>> On Friday 07 September 2012 02:17 PM, Romain Grecourt wrote:
>>>>> On 9/7/12 8:19 AM, Sahoo wrote:
>>>>>> Romain,
>>>>>>
>>>>>> Let me understand this better. If an external dependency is needed
>>>>>> by both some nucleus module and appserver module, do we have to
>>>>>> update dependencyManagement section of both nucleus/pom.xml and
>>>>>> appserver/pom.xml? Or, appserver/pom.xml extends nucleus/pom.xml?
>>>>> appserver/pom.xml extends nucleus/pom.xml. Nothing should be
>>>>> duplicated.
>>>> Well, we now have a multiple inheritance problem:
>>>>
>>>> closed/appserver -> open/appserver -> open/nucleus
>>>> closed/nucleus -> open/nucleus
>>>>
>>>> So, if something is needed by modules in closed/nucleus and
>>>> closed/appserver, then we have the same issue I mentioned in my
>>>> first email, don't we?
>>>>
>>>> Adding cloud module will only aggravate the issue.
>>>>
>>>> Thanks,
>>>> Sahoo
>>>
>>>
>>
>
>
>