True. Simple explanation is that I don't want the plugin to run on our
integration-tests, because they do a lot of stuff during the phase
'generate-test-resources' and 'process-test-resources'. And since these
tests don't have sources, I figured using a profile would be the easiest
way. That, or telling the plugin *not* to run, but this is not an option
on the plugin... :-(
On 10-06-11 23:14, Wendy Smoak wrote:
> On Fri, Jun 10, 2011 at 5:09 PM, Asmann, Roland<roland.asm...@adesso.at>
> wrote:
>> From what I've seen, the 'skip' parameter only exists on the
>> instrument-plugin, not on the report. I don't want it to trigger the
>> 'cobertura'-lifecycle, because this will trigger some other plugins that
>> are *very* slow.
>>
>> The reason I want this configured in the parent, is that I can't
>> influence all child-projects and I don't want to force all developers to
>> change much in their POMs. They are already chagrined that they have to
>> extend my POM, although they are starting to see the use of a common
>> parent...
>
> Still... it seems like whatever problem you're having, it's not about
> profile activation, it's more about getting something fixed in the
> Cobertura plugin, so that it does not 'kill the performance' of your
> build.
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
