Maybe an action after we seetle down the module renaming:
Maven 2.0.9 is out. This release as one interresting feature compared to
previous releases: it is bundled with fixed default version numbers for Maven
plugins. I.e. we could remove:
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4</version>
</plugin>
...
Since <version>2.4.2</version> is now implicit for anyone using Maven 2.0.9.
Reference: http://maven.apache.org/release-notes.html (scroll down to the first
point in "Changes that may affect existing builds").
Apache suggests to keep those <pluginManagement> around for stablier build, but
we know from experience that we usually fail to update their version number. We
could keep only the most sensitive ones or the ones we have an issue with, and
rely on the Maven defaults for the other. Plugins are then upgrated in bulk
only
when we upgrate Maven (reminder: the pre-2.0.9 behavior was to download the
latest version, which could happen at any time and sometime broke the build in
unpredicable way).
Maven 2.0.9 also have a new "import dependencies managements" feature that may
be of interest to projects depending on GeoTools like GeoServer and uDig:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
