Hi all, I just had a look at the pom & pluginMgmt declaration to see what could be upgraded. Sorry if this is obvious information, I'm crawled the archive a bit without finding the information.
*What's the current agreement about the minimum Maven version we would agree to support (I mean "by default", since it'd be overridable in some particular situations)?* Would this be ok to* add the <prerequisites> tag with Maven 2.2.1 tag* to the mojo-parent pom? My take on it is: defining m2.2.1 as the minimum is very reasonnable, as we anyway already have some minimum requirement about jdk1.5 in the pom (which 2.2.1 requires) and as that version is already almost 4 years old. And then, if we agree at least on some 2.2.1 minimum, I'd then propose upgrading plugins to their latest versions, as of: [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ mojo-parent --- [INFO] [INFO] The following plugin updates are available: [INFO] maven-checkstyle-plugin ............................... 2.9.1 -> 2.10 [INFO] maven-compiler-plugin .................................. 2.5.1 -> 3.1 [INFO] maven-dependency-plugin .................................. 2.6 -> 2.8 [INFO] maven-pmd-plugin ..................................... 2.7.1 -> 3.0.1 [INFO] maven-project-info-reports-plugin ........................ 2.6 -> 2.7 [INFO] maven-release-plugin ................................... 2.4 -> 2.4.1 [INFO] maven-site-plugin ........................................ 3.2 -> 3.3 [INFO] maven-surefire-plugin .................................. 2.13 -> 2.15 [INFO] maven-surefire-report-plugin ........................... 2.13 -> 2.15 [INFO] org.codehaus.mojo:license-maven-plugin ................... 1.4 -> 1.5 [INFO] org.codehaus.mojo:versions-maven-plugin ................ 1.3.1 -> 2.1 Based on that discussion, I'll see if I should start some vote about it. Thanks for your opinion. -- Baptiste
