We call ours the "standards" POM, as that's what's in there; it contains our standard plugin executions and default versions/scopes of certain artifacts (such as jsp-api) which are managed by the container.
On Fri, Mar 6, 2009 at 2:09 AM, Merv Green <[email protected]> wrote: > This post, > http://www.sonatype.com/people/2008/05/misused-maven-terms-defined/ , > points out that, like the Highlander, there can be only one Super pom. > > But "corporate pom" and "organizational pom" are just too hard to say. > > Choosing an extensible name seems handy; you could declare, for instance, > if you were mayor of Whoville, that all your developers inherit from > who-mother. If half your developers like the language Ham, and the other > half prefer Green Eggs, the Green Eggs guys could inherit from > green-eggs-mother, while the Ham people could inherit from mother-ham, both > of which inherit from who-mother. > > Other possibilities: > > Root pom > Top pom > Master pom > Team pom > One pom to rule them all > Org pom > Object pom > Grand pom > Base pom > Corp (Core?) (Corps?) pom > > So, what should I call my corporate pom? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
