One technique I've had work in the normal build plugins, that probably
would work in the reporting ones, is this:
Let's say the Cobertura report you're inheriting (from some parent pom,
I presume) is configured there with an
<execution>
<id>xyz</id>
(If it doesn't have this, then it is using some default id - you can
find out what it is by running once with the -X parameter, I think)
Then, configure your version of the plugin for Cobertura like:
<execution>
<id>xyz</id> <!-- must match the inherited one -->
<phase/> <!-- override the phase to be no-phase - this keeps
this from executing -->
I haven't tried this myself, but if you do, I'd like to know if it
succeeds in "getting rid of" this report :-)
-Marshall Schor
On 5/20/2010 4:38 PM, Timothy Mcginnis wrote:
> The skip helps. But there is one I'd like to get rid of, the Cobertura
> report. And it doesn't have a skip.
>
> Tim McGinnis
> 717 720-1962
> Web Development
> AES/PHEAA
>
>
>
> From:
> "Wendy Smoak" <[email protected]>
> To:
> "Maven Users List" <[email protected]>
> Date:
> 05/20/2010 04:33 PM
> Subject:
> Re: Preventing an inherited report from running
>
>
>
> On Thu, May 20, 2010 at 4:25 PM, Timothy Mcginnis
> <[email protected]> wrote:
>
>> I have a master pom that specifies the reports to be run. In one of the
>> child projects I do not want to run one of those reports. How do I
>> prevent it from running?
>>
> In general you can't un-inherit things, but some plugins have a "skip"
> parameter that you can configure.
>
> If that doesn't help, let us know what report it is and how it's
> configured...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
