Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Fri, 2 Apr 2004 4:24 PM
I think it was already fixed (fork was always on). However as I have alwso fixed
clover:on it should also work if you use clover:on standalone (i.e. without calling
clover:test).
---------------------------------------------------------------------
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: Closed
Priority: Minor
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Fix Fors:
1.5
Assignee: Vincent Massol
Reporter: Trygve Laugst?l
Created: Thu, 4 Dec 2003 9:24 PM
Updated: Fri, 2 Apr 2004 4:24 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]
