You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/10/25 22:05:27 UTC
[jira] [Updated] (SUREFIRE-1189) Prevent from I/O leakage. Thus
close streams in finally block.
[ https://issues.apache.org/jira/browse/SUREFIRE-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana updated SUREFIRE-1189:
-----------------------------------
Summary: Prevent from I/O leakage. Thus close streams in finally block. (was: Prevent from I/O leaked and close streams in finally block)
> Prevent from I/O leakage. Thus close streams in finally block.
> --------------------------------------------------------------
>
> Key: SUREFIRE-1189
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1189
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin, process forking, TestNG support, xml generation
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Fix For: 2.19.1
>
>
> On Sun, Oct 25, 2015 at 11:49 AM, Kristian Rosenvold-4 [via Maven] <ml...@n5.nabble.com> wrote:
> Based on code review I found a large number of close-statements that
> were not in the mandated finally blocks, which would create resource
> leakage on kill.
> I fixed this in bb99b232da0e93f2772be6945a410ea9ba666c4f, hope this
> will help the situation on windows.
> Kristian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)