dev@glassfish.java.net

Re: GlassFish parent pom changes

From: Sahoo <sanjeeb.sahoo_at_oracle.com>
Date: Fri, 07 Sep 2012 11:49:05 +0530

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?

Thanks,
Sahoo
On Friday 07 September 2012 02:28 AM, Romain Grecourt wrote:
> Everyone,
>
> /Note: the following information only applies to GlassFish/BG trunk,
> it's not related to GlassFish 3.x workspace./
>
> As of today GlassFish's parent pom (main/pom.xml) has been divided
> into Nucleus's parent pom (main/nucleus/pom.xml) and GlassFish
> Appserver's parent pom (main/appserver/pom.xml).
> GlassFish's parent pom is now used only to aggregate the build of
> nucleus and appserver.
>
> The properties and the dependency management sections have been
> separated as follow:
> - nucleus's pom does not contain anything related to JavaEE (except
> for Jersey as it is included in nucleus)
> - appserver's pom contains the rest.
>
> Please get back to me if you have any maven project/module inheriting
> GlassFish's parent pom that I'm not aware of, I'll help you ASAP.
> Also, do not hesitate to reach me if you have any question regarding
> those changes.
>
> Thanks!
> Romain