Adding dependencies to plugin in user's POM is old school for me, because this is "static" code. Look at Gradle they use script so it cannot be old school. Ask the Maven Users group and give them two things to choose: + static plugin dependencies + dynamic extension via scripts
In my f*g company we have surefire plugin and all plugins in top parent POM with configuration stuff and dependencies. This way I cannot customize my project because i don't have rights to change top parent POM. I cannot say this module has this extension, this and this another because the POM is static. But if I had script, I could write a trivial code there, or more complicated code in Java which appears in particular module or elsewhere and the script would becomes a reference to my object. That's flexibility. Even with script is better because the Surefire Users already reported JIRA bug that they want to customize surefire dependencies per execution. With static POM this is not possible. -- View this message in context: http://maven.40175.n5.nabble.com/Plugable-Softcoded-Customized-Maven-Plugins-tp5823365p5823485.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
