No Maven committers reading this list? Even a No would help.
Cheers,
Peter
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.html
Sent from the Maven - Users mailing list archive at Nabble.com
, 2010 at 11:08 PM, Peter Niederwieser pnied...@gmail.com wrote:
No Maven committers reading this list? Even a No would help.
Cheers,
Peter
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.html
reading this list? Even a No would help.
Cheers,
Peter
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.html
Sent from the Maven - Users mailing list archive at Nabble.com
, and Gradle builds.
Cheers,
Peter
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3286870.html
Sent from the Maven - Users mailing list archive at Nabble.com
Over time, I have written several Maven plugins that configure other plugins by
manipulating their configuration section (with the Xpp3Dom API). This
technique has often proved to be a life saver. For example, I have a plugin
that determines dynamically which JUnit tests should be run, and
. Is this an intentional change? And what is the
alternative?
Cheers,
Peter
PS: Is there any documentation about writing plugins for Maven 3 (Guice DI,
new APIs, breaking changes, etc.)? Can't find anything.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic
This is a good example of my belief, that it should be possible to
invoke other plugins dynamically by supplying an own configuration
section from your own plugin.
On Thu, Nov 25, 2010 at 6:00 AM, Peter Niederwieser pnied...@gmail.com wrote:
Over time, I have written several Maven plugins that
