You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2005/04/04 19:35:56 UTC
[jira] Closed: (MPCLOVER-33) There should be a property to turn off Clover
[ http://jira.codehaus.org/browse/MPCLOVER-33?page=history ]
Vincent Massol closed MPCLOVER-33:
----------------------------------
Resolution: Won't Fix
Assign To: Vincent Massol
Closing as it's already possible to do this by not adding the clover report to the project who don't want it...
> There should be a property to turn off Clover
> ---------------------------------------------
>
> Key: MPCLOVER-33
> URL: http://jira.codehaus.org/browse/MPCLOVER-33
> Project: maven-clover-plugin
> Type: Improvement
> Environment: Maven 1.0.2
> Reporter: Wim Deblauwe
> Assignee: Vincent Massol
>
>
> It would be convenient to have a property (e.g. maven.clover.enabled) to turn Clover on or off. This is especially handy when using Clover with the multiproject plugin when some of the projects are not java projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: There are many ways to skin the skin the cat - WAS Re: [jira] Closed: (MPCLOVER-33) There should be a property to turn off Clover
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Siegfried,
The current solution is to have different <projects> sections for different
needs. To my knowledge this is the only solution that currently exists.
What you are really asking it seems is a generic way to express that you do
not want a specific report for a specific project. This is not related to
the dashboard project. This is true for any report.
So you'd like to say: inherit all those reports except these few ones.
Before deciding to add special properties to all plugin that generate
reports I'd prefer we all agree on a strategy to express your use case.
ATM, why don't you use different project.xml. For example:
common/
|_ top.xml
|_ full_reports.xml (extends top.xml)
|_ limited_reports.xml (extends top.xml)
Mysubproject1
|_ project.xml (extends ../full_reports.xml)
Myspecialsubproject2
|_ project.xml (extends ../limited_reports.xml)
I guess using xml entity includes would also work (but not for m2 but then
there are probably other mechanisms in m2 for your usecase).
What do others think?
Thanks
-Vincent
> -----Original Message-----
> From: Siegfried Goeschl [mailto:siegfried.goeschl@it20one.at]
> Sent: lundi 4 avril 2005 19:56
> To: Maven Developers List; Vincent Massol
> Subject: There are many ways to skin the skin the cat - WAS Re: [jira]
> Closed: (MPCLOVER-33) There should be a property to turn off Clover
>
> Hi Vincent,
>
> it is quite common to use POM inheritance defining the reports and use a
> few exceptions :
>
> +) in fulcrum-cache there is a seperate report section to avoid the
> JCoverage plugin during the long running tests since it uses POM
> inheritance. And it drives me nuts that I have to disable my broken
> SIMIAN report in two project.xml
>
> +) for one of my customers I also have to redefine the reports since it
> would measure tons of Torque-generated code while I'm only interested
> that the connectivity and accessing all tables works
>
> I think the question is not necesarry if it is already possible but if
> it is in general sensible to turn off a report using a property .... :-)
>
> Thanks in advance
>
> Siegfried Goeschl
>
> Vincent Massol (JIRA) wrote:
>
> > [ http://jira.codehaus.org/browse/MPCLOVER-33?page=history ]
> >
> >Vincent Massol closed MPCLOVER-33:
> >----------------------------------
> >
> > Resolution: Won't Fix
> > Assign To: Vincent Massol
> >
> >Closing as it's already possible to do this by not adding the clover
> report to the project who don't want it...
> >
> >
> >
> >>There should be a property to turn off Clover
> >>---------------------------------------------
> >>
> >> Key: MPCLOVER-33
> >> URL: http://jira.codehaus.org/browse/MPCLOVER-33
> >> Project: maven-clover-plugin
> >> Type: Improvement
> >> Environment: Maven 1.0.2
> >> Reporter: Wim Deblauwe
> >> Assignee: Vincent Massol
> >>
> >>
> >
> >
> >
> >>It would be convenient to have a property (e.g. maven.clover.enabled) to
> turn Clover on or off. This is especially handy when using Clover with the
> multiproject plugin when some of the projects are not java projects.
> >>
> >>
> >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
There are many ways to skin the skin the cat - WAS Re: [jira] Closed:
(MPCLOVER-33) There should be a property to turn off Clover
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Vincent,
it is quite common to use POM inheritance defining the reports and use a
few exceptions :
+) in fulcrum-cache there is a seperate report section to avoid the
JCoverage plugin during the long running tests since it uses POM
inheritance. And it drives me nuts that I have to disable my broken
SIMIAN report in two project.xml
+) for one of my customers I also have to redefine the reports since it
would measure tons of Torque-generated code while I'm only interested
that the connectivity and accessing all tables works
I think the question is not necesarry if it is already possible but if
it is in general sensible to turn off a report using a property .... :-)
Thanks in advance
Siegfried Goeschl
Vincent Massol (JIRA) wrote:
> [ http://jira.codehaus.org/browse/MPCLOVER-33?page=history ]
>
>Vincent Massol closed MPCLOVER-33:
>----------------------------------
>
> Resolution: Won't Fix
> Assign To: Vincent Massol
>
>Closing as it's already possible to do this by not adding the clover report to the project who don't want it...
>
>
>
>>There should be a property to turn off Clover
>>---------------------------------------------
>>
>> Key: MPCLOVER-33
>> URL: http://jira.codehaus.org/browse/MPCLOVER-33
>> Project: maven-clover-plugin
>> Type: Improvement
>> Environment: Maven 1.0.2
>> Reporter: Wim Deblauwe
>> Assignee: Vincent Massol
>>
>>
>
>
>
>>It would be convenient to have a property (e.g. maven.clover.enabled) to turn Clover on or off. This is especially handy when using Clover with the multiproject plugin when some of the projects are not java projects.
>>
>>
>
>
>