[ http://jira.codehaus.org/browse/SUREFIRE-25?page=comments#action_70307 ] 
            
codehauser commented on SUREFIRE-25:
------------------------------------

Still seeing this issue (null directory hanging out) in plugin:

  <artifactId>maven-surefire-plugin</artifactId>
  <packaging>maven-plugin</packaging>
  <name>Maven Surefire Plugin</name>
  <version>2.2</version>

Thanks!

> surefire property droppings in fork mode
> ----------------------------------------
>
>                 Key: SUREFIRE-25
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-25
>             Project: surefire
>          Issue Type: Bug
>    Affects Versions: 1.5.2
>            Reporter: Brett Porter
>         Assigned To: Brett Porter
>             Fix For: 2.0
>
>
> 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

        

Reply via email to