Hi Sven,

Sven Preßler wrote:

> You might want to take a look at the maven-inherit-plugin:
> http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin/

Honestly, this plugin leads directly into Maven plugin dependency hell. If
you like to have arbitrary side effects in multi-project builds, well, go
ahead and use it - otherwise stay as far away as you can.

Why? Maven will load each plugin only once. Now, if you write an extension
to the maven-compiler-plugin and refer e.g. version 2.0 as dependency and
in your POM you declare the maven-compiler-plugin with version 2.2, it
depends on your build order which version of the compiler plugin is used.
However, from your POM you'll never ever recognize that this extension will
actually inject an old version of the maven-compiler-plugin and it might
simply fail on unknown configuration elements or the other way round, your
extension plugin can fail, because the newer version is no longer
compatible (Maven plugins are never required to be binary compatible).

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to