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 2003/12/05 04:25:55 UTC

[jira] Created: (MPCLOVER-13) The clover should fork the junit tests

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
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

   Assignee: 
   Reporter: Trygve Laugst?l

    Created: Thu, 4 Dec 2003 9:24 PM
    Updated: Thu, 4 Dec 2003 9: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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org