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/BuildC >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]
