Wait, these are different issues, right? Switching to java.nio would have been possible prior to Java 7, right? And it's probably a non-trivial project to try that out, as compared to try-with-resources and multiple exceptions which are basically code clean-ups. Should we split up this ticket into one for java.nio (not a child of #17822 (moved)) and one for try-with-resources and multiple exceptions (child of #17822 (moved))?
... Should we split up this ticket into one for java.nio (not a child of #17822 (moved)) and one for try-with-resources and multiple exceptions (child of #17822 (moved))?
Yes, except that both should be under #17822 (moved). There were some changes to nio in java7 that are imporant here. But, as long as that is investigated it could be without the parent.
Ticket #20395 (moved) is going to use NIO. This ticker was meant as a placeholder and now there is a concrete issue.
Closing.
Please re-open, if I missed anything.
Trac: Status: new to closed Resolution: N/Ato duplicate