> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: dimanche 12 juin 2005 12:10
> To: 'Maven Developers List'
> Subject: [m2] Getting a plugin declared dependency from java (was RE:
> lifecycle design: clover and other use cases)
[snip]
> [...] now the question is how do I dynamically add the
> Clover dependency so that the CompilerMojo can add it to its compilation
> classpath?
>
> I've added:
>
> /**
> * @parameter expression="${project.compileClasspathElements}"
> * @required
> */
> private List compileClasspathElements;
>
> to get the compile classpath list but I don't know how to query the
> plugin's
> own POM to get the Clover dependency (the equivalent of
> ${...getDependencyClasspath('clover:clover')} for m1).
>
> Any idea?
I think I got it:
/**
* @parameter expression="${project.artifacts}"
* @readonly
*/
private Set dependencies;
However ${project} will reference the project using the plugin and now the
plugin itself right? Can I use ${plugin} as in m1? (I'll try it now).
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
