The following comment has been added to this issue:
Author: Vincent Massol
Created: Fri, 5 Dec 2003 12:14 PM
Body:
Ah yes, I think I understand. That's because clover flushes its coverage buffer on JVM
exit. Thus if you generate the report right after running the tests, you will miss
some test coverage. Forking the tests let them run in another JVM and thus the clover
data is flushed before the report is generated.
See http://www.thecortex.net/clover/FAQ.html
We could force the unit tests to be run in a separate JVM or use an interval flush
policy.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCLOVER-13
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCLOVER-13
Summary: The clover should fork the junit tests
Type: Improvement
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Fix Fors:
1.5
Assignee:
Reporter: Trygve Laugst?l
Created: Thu, 4 Dec 2003 9:24 PM
Updated: Fri, 5 Dec 2003 12:14 PM
Description:
I was having problems with getting the correct values in the clover
report and was told that I needed to fork the unit tests while running the report.
As most unittests doesn't need to run in their own jvm I would like it if the default
clover report behaviour was to fork a jvm.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
