On Tuesday 29 September 2009 14:19, Jörg Schaible wrote: > Roland Asmann wrote at Dienstag, 29. September 2009 13:12: > > OK, so maybe I should've written a bit more about what I meant. > > > > I indeed meant to create a normal jar-dependency on the plugin and write > > your own plugin. However, that plugin could very well extend the mojo > > from the original and use any other classes from the extended plugin. I > > mean, it's just java! > > No you cannot! Every plugin is loaded only once. If you derive from a > plugin, you will load the other one implicitly. So, what happens now, if > your user want/have to use the original plugin in a different version than > the version required by the derived plugin? You will easily break one of > the two plugins and give your user a hard time, really!
Really? I had no idea... Good to know. I'll be developing a couple of plugins in my company over the next couple of weeks, so that's a thing to remember! > > > And sharing the data is nice, but if you need something from an existing > > plugin, you'd have to convince the authors of that plugin to write it for > > you. So that doesn't solve anything! > > You can copy the source as long as the functionality is not separated into > an own artifact. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [email protected] Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
