Vincent Massol wrote: >Hi Brett, > >Thanks for your help on this for the clover plugin. > > Sorry it took so long...
>I agree. I don't understand "This allows a plugin to add a plugin:descriptor >goal". Why cannot this be done by the @phase tag in the mojo? > > Something needs to activate the plugin plugin in the lifecycle. This would mean specifying the plugin:plugin goal in your build section. It's not already activated by packaging, as jar:jar is used to do that. >I'm not sure I understand the "@executePhase <somephase>" tag? Is it like a >m1 prereqs in that it tells m2 to execute the <somephase> phase before >executing the mojo goal? > Yes, it is sort of a prereq, except that it is always executed if the other goal is attained, and there is only one. It's better thought of as a clean, parallel invocation of the lifecycle. It's currently being used in idea:idea to ensure generate-sources is called. >I don't understand the concept of the "lifeycle >cloning" though. What does it mean? Why is it required (probably not to >interfere with something but with what)? > > It is cloned so that its effects don't come back into any other goals that didn't want them. Each goal on the command line is considered independant of the others. >"Desired use: >- m2 clover:clover > 1) register clover compiler goal into generate-sources > 2) modify output directory > 3) run test (based on executePhase) > 4) report database later reused" > >Does this cover the following m1 use case: "maven clover:on war clover:off"? > > So you can include those classes in the WAR? Yes. Just set a different executephase, and change the finalName. >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'll comment more on the rest when I understand more about the above. > > Thanks, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
