I would like to configure surefire's providers in the plugin configuration.
My problem is that the aggregator POM defines surefire version in
pluginManagement, and the surefire's dependency has to declare the same
version.
This can be done via property ${surefire.version} antipattern. Then the
pluginManagement lost its own purpose.
Other solution is to declare the provider in the plugin's dependency in the
pluginManagement. The problem here is that you cannot exclude it in children
because the dependency is global.
I would like to have a new parameter "providers" declaring
[groupId:]artifactId.
I think the users will appreciate because of simple configuration.
No need for provider version because it's inherited from the plugin.
One can declare other provider per plugin execution section.
Pls let me know the pros/cons and problems if you are facing any with new
parameter.
-----
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/SUREFIRE-Configurable-Providers-tp5812529.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
