You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/25 19:00:29 UTC
[jira] Created: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Versions:
1.5
Assignee:
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Fri, 25 Jun 2004 1:00 PM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Vincent Massol (mailto:vmassol@pivolis.com)
Date: Wed, 9 Feb 2005 3:02 PM
Changes:
assignee changed to Vincent Massol
Version changed to 1.6
Version changed from 1.5
Fix Version changed from 1.7
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPCLOVER-18?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Versions:
1.6
Assignee: Vincent Massol
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Wed, 9 Feb 2005 3:02 PM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Commented: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Matt Read
Created: Thu, 10 Feb 2005 8:55 AM
Body:
Yep, that would solve my immediate (well, immediate 7 months ago) problems.
I agree with you completely on your general consideration point. For the kind of projects that I'm generally involved with, Maven simply will not scale sufficiently to support continuous integration. I find myself slipping back to nightly builds for more and more of the goals as the codebase grows.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPCLOVER-18?page=comments#action_29759
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Versions:
1.6
Assignee: Vincent Massol
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Thu, 10 Feb 2005 8:55 AM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Commented: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Matt Read
Created: Thu, 10 Feb 2005 7:24 AM
Body:
It's been some time since I posted this but from memory I thought that once the clover report was registered, all compilations had the effect of instrumenting the code. Are suggesting that code actually gets completely recompiled on the second (clover) run of the tests?
If this is true then with just a fairly comprehensive test suite on a medium sized application, my build is simply doing too much stuff. On a larger application it becomes impractical to use Maven to get my build metrics using continuous integration.
On an XP/Agile project I regularly allocate time to refactor/optimise my test suite in order to decrease the execution time and therefore encourage regular runs of the tests. The impact of running the suite multiple times can be huge.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPCLOVER-18?page=comments#action_29752
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Versions:
1.6
Assignee: Vincent Massol
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Thu, 10 Feb 2005 7:24 AM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Closed: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Fri, 11 Feb 2005 10:52 AM
Done. Added new maven.clover.execute.during.report (defaults to true).
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Closed
Priority: Minor
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Fix Fors:
1.7
Versions:
1.6
Assignee: Vincent Massol
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Fri, 11 Feb 2005 10:52 AM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Vincent Massol (mailto:vmassol@pivolis.com)
Date: Fri, 16 Jul 2004 2:49 PM
Changes:
Fix Version changed to 1.6
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPCLOVER-18?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Fix Fors:
1.6
Versions:
1.5
Assignee:
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Fri, 16 Jul 2004 2:49 PM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Commented: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Vincent Massol
Created: Thu, 10 Feb 2005 7:37 AM
Body:
General considerations:
I've always found this to be an issue with Maven reports: they not only create a report but they do also perform the logic to create the report data. Thus if you build your project and then generate the site you'll have run twice the build logic that creates the report data.
For your problem:
The only solution I can think of is to have an execute.during.report flag (as you mentioned) so that instrumentation would only happen if this flag is set. If not, the report will take whatever data has already been generated in the Clover database file (which could amount to nothing).
Now in term of sharing the compilation with the junit report, it will be possible by doing the following:
- set maven.clover.execute.during.report = false
- call 'maven clover:on site' instead of 'maven site'
Would that be ok with you?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPCLOVER-18?page=comments#action_29755
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Versions:
1.6
Assignee: Vincent Massol
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Thu, 10 Feb 2005 7:37 AM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Commented: (MPCLOVER-18) Stop Clover re-running tests if they've already run
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Vincent Massol
Created: Wed, 9 Feb 2005 3:01 PM
Body:
Hi Matt,
Yes, the tests are executed twice but not in the same condition. One time it is without clovering on (i.e. the source code is not instrumented) and the second time clovering is on, the code is instrumented and the tests are generating clover data which are then used by the clover report to produce some HTML file.
I'm probably missing something though... :-)
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPCLOVER-18?page=comments#action_29716
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
Type: Wish
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Versions:
1.6
Assignee:
Reporter: Matt Read
Created: Fri, 25 Jun 2004 1:00 PM
Updated: Wed, 9 Feb 2005 3:01 PM
Description:
If both the junit-report and clover-report are registered the tests execute twice. Would it be possible to either provide a setting to disable this or detect whether tests have already been run?
This might be similar to the property in the Cactus plugin - cactus.execute.during.report.
Thanks,
Matt.
---------------------------------------------------------------------
JIRA INFORMATION:
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