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!
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! On Tuesday 29 September 2009 13:05, Stephen Connolly wrote: > That guess would be wrong. > > You cannot extend plugins in a different group id. you need to create a > standard jar dependency and have your plugins be thin wrappers on top of > the jar dependency. > > If multiple plugins need to share data, AFAIK they should store that data > in MavenSession > > -Stephen > > 2009/9/29 Roland Asmann <[email protected]> > > > My guess would be to write a plugin that depends on this plugin... Then > > you should be able to connect to all the public and (if you extend a > > class) protected methods... Or do you have a reason why that would/could > > not work? > > > > On Tuesday 29 September 2009 12:00, Vadim wrote: > > > Hello, > > > In my plugin I need to construct a classpath containing artifacts in > > > the pom of the project being analyzed. There's a > > > maven-dependency-plugin > > > > which > > > > > already does the specified task > > > (BuildClasspathMojo< > > > > http://svn.apache.org/viewvc/maven/plugins/tags/maven-d > > > > >ependency-plugin-2.1/src/main/java/org/apache/maven/plugin/dependency/Bu > > >ildC lasspathMojo.java?view=markup>). The question is: how do I reuse > > > this functionality in my plugin? > > > > > > I've searched unsuccessfully for the explanation on how the interop > > > > between > > > > > different maven plugins should happen. > > > This< > > > > http://mail-archives.apache.org/mod_mbox/maven-users/200706.mbox/%3C46 > > > > >[email protected]%3e>thread mentions that directly invoking > > > mojos from plugins is a bad practice as it increases coupling between > > > plugins > > > > and > > > > > prohibits reuse (as plugins should be merely maven-specific wrappers of > > > existing functionality). Some form of context, shared between plugins > > > is mentioned, but I failed to find any documentation on how to use it. > > > However (as I understood - and I might be wrong) this context is only > > > shared between plugins configured in the pom and can't be used by > > > plugins invoking other plugins directly. > > > > > > I would be grateful if someone could point me in right direction. > > > > -- > > 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] -- 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]
