If you're interested in applying them, I could create some JIRA patches
to improve your current pom.xml's.
I've maven2ized http://spring-rich-c.sf.net , http://networktools.sf.net
and several other projects.
With kind regards,
Geoffrey De Smet
Mark Proctor wrote:
We use pom's for dependency management, but actually build wtih ant
(which can use maven), we just haven't updated the pom as our day to day
work is done in eclipse - where it doesn't matter as much.
Mark
Geoffrey De Smet wrote:
Are you guys using maven2 or ant for building the trunk?
I noticed the pom.xml's are "3.0.2" instead of "3.1.0-SNAPSHOT", so I
am fear the dependency versions will be out of date too?
Also, I noticed you didn't lock down the maven plugin versions, which
can lead to instable maven2 builds. I do that like this in the parent
pom:
<build>
<pluginManagement>
<plugins>
<!--
Last time synchronized with the latest plugin
releases:
2006-06-21
See
http://news.gmane.org/gmane.comp.apache.maven.announce
-->
<!-- Building -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-help-plugin</artifactId>
<version>2.0.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>2.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>2.2</version>
</plugin>
...
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
