Although the question wasn't addressed to me, I have run into some
problems (hence the question in the first place) so just adding my 2c.
If the super pom modeled as a top level module (ie. each project
declares it as a parent), I get into a lot of issues when using the
release plugin for the individuaal projects (You can just try it out to
see what I mean). One of the issues I also get into is that the cvs
repository needs to be structured with the superpom module at the top
and each of the projects as a sub directory in the cvs module
representing the super pom which is not exactly the most convenient
mechanism for conducting version control across multiple independent
projects.
Having said that since maven itself does use a super pom which does not
suffer from these limitations hopefully there's some way to implement -
but I couldn't figure it out so far.
Dhananjay
Roald Bankras wrote:
Nathan
What kind of problems did you ran into? I'm currently working on a super pom
for my company, but haven't seen any problems yet.
Roald Bankras
Software Engineer
JTeam b.v.
-----Original Message-----
From: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 20, 2006 12:29 AM
To: Maven Users List
Subject: RE: How to implement an organisational super pom ?
>From my adventures in trying to do this, I've found that it's just not a
good idea in the current state of things. There are some things that can
be done with dependencyManagement and pluginManagement, but that only
goes so far.
My suggestion is to standardize things via archetypes to generate POMs
in a certain fashion. For common "automated build" stuff use profile
settings for the build user.
-Nathan
-----Original Message-----
From: Dhananjay Nene [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 1:34 PM
To: Maven Users List
Subject: How to implement an organisational super pom ?
I need to implement a common pom which can be inherited by a large
number of projects. However the common pom does not reflect a top level
module and does not have any sources or artifacts (since it is used only
for inheritance). My attempts so far lead me to believe that maven
requires me to assign a version to the common pom, and the release
management workflow tries to checkout a project corresponding to top
level pom which obviously fails in my case. How can I implement a common
pom (like the maven super pom) so that the common pom is used only for
inheritance, and each pom which refers to it (as a parent ??) is in fact
a top level application (and not a module/sub module) ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-----------------------------------------
CONFIDENTIALITY NOTICE This message and any included attachments
are from Cerner Corporation and are intended only for the
addressee. The information contained in this message is
confidential and may constitute inside or non-public information
under international, federal, or state securities laws.
Unauthorized forwarding, printing, copying, distribution, or use of
such information is strictly prohibited and may be unlawful. If you
are not the addressee, please promptly delete this message and
notify the sender of the delivery error by e-mail or you may call
Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
(816)221-1024. -------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
