I also find this quite interesting. I did some plugin development this
spring, and I several times thought to myself "this is already done in
<plugin-name>. If I am doing this I am duplicating code". In particular
I was making a plugin which should compile some intermediary AspectJ
sources without the user needing to worry about it, so it would be nice
to call the compile mojo of the aspectj-maven-plugin and inject
necessary configuration to adapt it to my use instead of coding my own
compile mojo which used the AspectJ API (and looked very much alike the
source of aspectj-maven-plugin).
I think I remember I've read somewhere that plugins should not depend on
other plugins though. I will remember your inherit-plugin the next time
I do plugin development :)
-Rune
Brian E. Fox wrote:
This is interesting functionality that the dev team should be aware of.
I know it's frequently asked how to extend a plugin.
--Brian
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart
McCulloch
Sent: Tuesday, September 25, 2007 11:21 AM
To: Maven Users List
Subject: mojo inheritance
Hi,
I've developed a small plugin that lets you extend mojos from other
maven
plugins by merging the plugin metadata:
http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin/index.h
tml
I've successfully used this to extend various core plugins - is anyone
interested in this approach (or is it a bad idea?)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
