maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <>
Subject [jira] (SUREFIRE-1031) Temp files are not deleted properly
Date Thu, 02 Jan 2014 01:14:45 GMT


Andreas Gudian closed SUREFIRE-1031.

    Resolution: Fixed

Having a rather small SSD myself, running the surefire-integration tests repeatedly forced
me to delete those files manually as well... PITA ;)

I fixed it, but only {{deleteOnExit()}} did the trick, and so we'll have to wait for the VM
to shut down... ;). That said, you might still see undeleted files in case your mvn process
exits unexpectedly (crash, or someone calling {{Runtime.halt()}}).

Committed in 21737b868ea65f33d28fa8f4499585397a0a966d. Care to give it a try?
> Temp files are not deleted properly
> -----------------------------------
>                 Key: SUREFIRE-1031
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.15, 2.16
>            Reporter: Vjatseslav Rosin
>            Assignee: Andreas Gudian
>             Fix For: 2.17
> After the SUREFIRE-938 fix was introduced in version 2.15 there is a problem of two much
temp files created in the temp folder. This is related to this issue in DeferredFileOutputStream
of common-io:
> As a workaround it would be nice to have a configuration option for memory threshold
size instead of hardcoded 1MB.
> Another solutions would be do delete the temp file explicitly (if it exists) before closing
the DeferredFileOutputStream.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message