You are viewing a plain text version of this content. The canonical link for it is here.

Posted to surefire-dev@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/01/02 17:21:13 UTC

[jira] Updated: (SUREFIRE-25) surefire property droppings in fork mode

     [ http://jira.codehaus.org/browse/SUREFIRE-25?page=all ]

Carlos Sanchez updated SUREFIRE-25:
-----------------------------------

              Version: 1.5.2
    Testcase included: yes

test1 in the surefire plugin can be used as test case

> surefire property droppings in fork mode
> ----------------------------------------
>
>          Key: SUREFIRE-25
>          URL: http://jira.codehaus.org/browse/SUREFIRE-25
>      Project: surefire
>         Type: Bug

>     Versions: 1.5.2
>     Reporter: Brett Porter
>     Assignee: Jason van Zyl

>
>
> when running surefire in fork mode (specifically, I'm using cobertura), the surefire.properties, surefire-classloader.properties and sometimes a file called "null" get left behind. I believe this might be when the tests fail but haven't investigated.
> I think these files should either be created in the tmpdir (preferred) or target, and set to delete on exit rather than delete on success.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira