Josh Suereth wrote:
I'm guessing maven 2.1.0 is performing some new check
Plugin JARs contain a plugin descriptor in META-INF/maven/plugin.xml which includes the plugin version. As per MNG-3284, this version is taken into account when loading plugins.
1) This is actually an issue with the shitty plugin
It was reported some time ago in MSHITTY-10.
2) I should be using some other form of integration testing for maven 2.1.0
The Maven Invoker Plugin [0] could be an alternative. To separate the plugin JAR under test from the local repository, it supports usage of a dedicated test repository instead of changing the plugin version. In general, the Invoker Plugin also supports Groovy-based hook scripts (using Groovy 1.5.6) though I can't tell what differences in detail one would encouter when migrating. One thing to watch out for would be to have each script "return true" because void/null is currently interpreted as a failure by the Invoker Plugin.
Benjamin [0] http://maven.apache.org/plugins/maven-invoker-plugin/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
