> -----Original Message----- > From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] > Sent: dimanche 12 juin 2005 12:12 > 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... > > From the Modello Maven plugin[1]: > > project.addCompileSourceRoot( outputDirectory ); > > where project is declared like this: > > /** > * @parameter expression="${project}" > * @required > */ > private MavenProject project; Cool thanks. However I still need to find out how to retrieve from java code a dependency declared in a plugin's POM. On IRC, you've pointed me to http://jira.codehaus.org/browse/MNG-455. For now, I've added the clover dep to the project using the Clover plugin but that's really a temporary solution. I'd love to find how to implement this properly. [snip] > > Also, could you please explain what @requiresDependencyResolution means? > > By having this tag Maven will make sure that all the dependencies of a > project is downloaded. This is what makes the clean plugin not download > all dependencies before execution. Hmm... My clover plugin does not have this tag but it still downloads the clover dependency when called. What am I missing? [snip] > > > >How do you tell clover:clover that it should execute the war goal or > > > >anything else for that matter? > > > > > > > > > > > <executePhase/>. This part may require more thought - I have a bunch > of > > > alternative ideas locally - these seemed the best to me, but if there > > > are any holes then I'm up for changing it. > > > > I still don't understand this. Has this been firmed up throught the > > recent design talks? > > Think of executePhase as a separate invocation of Maven. When running the > idea plugin (which has executePhase=generate-resources) Maven will execute > the generate-sources and generate-resources phases. Each plugin that has > @phase=generate-sources or generate-resources will also execute in this > subexecution and thus properly add any generates sources directories to > the compile sources set. I must be dumb... I still don't get it... :-) Are you saying that executePhase is required whenever you have several plugins bound to the same phase so that they all properly execute? What do you mean by "when running the idea plugin"? By calling some idea plugin goal or by calling a lifecycle that comes after the generate-sources/resources one? Thanks Trygve! -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]