Thanks for the answers, I will describe the solution I'll choose. On Wed, Sep 30, 2009 at 12:27 AM, Neroon <[email protected]> wrote:
> Have you had a look at the following? > http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin/ > > I haven't actually tried it, but it looks promising. The information is > from > this issue: > http://jira.codehaus.org/browse/MNG-3042 > > Cheers > > Am Dienstag, 29. September 2009 schrieb Vadim: > > 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- > dependency- > > plugin-2.1/src/main/java/org/apache/maven/plugin/dependency/BuildClasspathMojo.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/%[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. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
