In m3 if you activate the // mode and you have a plugin which isn't marked as compatible you'll have a warning like that :
[WARNING] ***************************************************************** [WARNING] * Your build is requesting parallel execution, but project * [WARNING] * contains the following plugin(s) that are not marked as * [WARNING] * @threadSafe to support parallel building. * [WARNING] * While this /may/ work fine, please look for plugin updates * [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in * [WARNING] * question, not against maven-core * [WARNING] ***************************************************************** [WARNING] The following plugins are not marked @threadSafe in Maven Model: [WARNING] org.apache.maven.plugins:maven-resources-plugin:2.4.2 [WARNING] org.apache.maven.plugins:maven-clean-plugin:2.3 [WARNING] org.apache.maven.plugins:maven-compiler-plugin:2.0.2 [WARNING] org.apache.maven.plugins:maven-install-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-surefire-plugin:2.4.3 [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-remote-resources-plugin:1.1 [WARNING] org.codehaus.modello:modello-maven-plugin:1.3 Arnaud On May 17, 2010, at 11:42 PM, Paul Benedict wrote: > Lots of plugins are up for vote to be @threadSafe with Maven 3. Does > Maven 3 have any mechanism to reject plugins prior to the versions > being released? What happens if someone uses a Maven 2 version? > > Paul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
