maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Rosenvold <>
Subject Re: Plugable/Softcoded/Customized Maven Plugins
Date Wed, 14 Jan 2015 12:15:44 GMT
Anders; we are discussing how the maven owl can support /both/ shotgun
*and* BFG9000 :) I sense there's small adjustments we could make
"somewhere" that could make the plugin model less monolithic.


2015-01-14 13:13 GMT+01:00 Anders Hammar <>:
>> 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.
> Sure you can. Just specify the artifact as a dep to the plugin in that
> module and it will be added to the mojo's classpath (in addition to
> anything specified in parent).
> IMHO this is the Maven way. And if you don't follow it the Maven owl will
> grab it's shotgun and hunt you down...:-)
> /Anders
>> 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:
>> Sent from the Maven Developers mailing list archive at
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message