[ http://jira.codehaus.org/browse/SUREFIRE-25?page=comments#action_61149 ]
Derek Slife commented on SUREFIRE-25: ------------------------------------- I'm still having this issue using 1.5.3-SNAPSHOT. After some initial investigation, it seems like the deteleOnExit within loadProperties() is failing. I added a deleteOnExit to the file references within getForkArgs() also. After that change, it finally deleted the droppings. > 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 > Fix For: 1.5.2 > > > 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
