In our super pom we have the following elements:
<prerequisites>
<maven>2.0.7</maven>
</prerequisites>
So each developer has at least the recommended version of maven.
Two profiles, one default on, which defines our artifactory as central and
takes care of the distribution management and one "athome" which doesn't define
our artifactory as central repository.
Pluginmanagement section, which nails down all the versions of the plugins we
use.
Reporting section, so the generated sites of the projects have the same layout,
same settings, etc.
Dependencymanagement, so all the projects use the same dependendency versions.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-----Original Message-----
From: Benjamin Voigt [mailto:[EMAIL PROTECTED]
Sent: Wed 7/2/2008 08:58
To: [email protected]
Subject: Best practices for corporate poms
Hello,
I'd like to know the best practices for using a corporate or a
company-wide pom, e.g. what do you put in it except for
distributionManagement ?
I've read that some people don't use SNAPSHOT versions for the corporate
pom and instead only increase a single number for every new version of
the corporate pom (e.g. version 2 to 3 to 4 etc.).
Maybe those facts could be documented somewhere on the maven site (like
a how to).
Every idea is appreciated :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
