> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: dimanche 12 juin 2005 11:53
> To: 'Maven Developers List'
> Subject: RE: lifecycle design: clover and other use cases
[snip]
> Now the issue is that those generated files are not yet picked up by the
> compiler:compile goal. I'm about to try modifying the
> ${project.compileSourceRoots} in CloverMojo but I don't know if that'll
> have any effect on the CompilerMojo...
Actually it did work but 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?
[snip]
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
