Jason van Zyl wrote on Wednesday, September 26, 2007 7:59 AM: > On 25 Sep 07, at 10:21 PM 25 Sep 07, 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. >> > > We could definitely integrate this method, would be highly useful. > > When we integrate the anno-mojo stuff we'll have this with > annotations but doing this with the existing mechanism would be good.
Just as a heads-up: This is only useful if it does not knock down the plugin version of the re-used plugin! We have currently such a situation with the XDoclet plugin that uses classes from the Antrun plugin. We need features from Anrun plugin 1.1, but the XDoclet plugin references Antrun plugin 1.0. For us the modules using the Antrun plugin suddenly fail, if a module using the XDoclet plugin runs first. In the end we used a locally modified version of the XDoclet plugin that contains a copy of the referenced classes of the Antrun plugin (with different package name) to get things running. Since we're still forced to run M205 things might have been improved regarding class loaders, but I'd bet the situation for plugin inheritance is still the same. So you should be *very* careful with such a functionality. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
