Azzurite / evolutionchamber

Automatically exported from code.google.com/p/evolutionchamber
0 stars 0 forks source link

FileInputStream is not closed after a call to Properties.load #209

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run the UserSettings test suite.
2. Run the same test suite again.

What is the expected output? What do you see instead?
I expect all the tests to pass in both runs.
The tests fail to delete DOES_NOT_EXIST.properties and EMPTY.properties after 
each run.

The anonymous FileInputStream remains closed after the invocation of 
Properties.load according to the docs.

From java.util.Properties.load(InputStream inStream):
"The specified stream remains open after this method returns."

Original issue reported on code.google.com by netpr...@gmail.com on 13 Jul 2011 at 10:27

GoogleCodeExporter commented 8 years ago
The same problem exists for Properties.store()

"After the entries have been written, the output stream is flushed. The output 
stream remains open after this method returns."

Original comment by netpr...@gmail.com on 13 Jul 2011 at 10:38

GoogleCodeExporter commented 8 years ago
Fixed in r290

Original comment by netpr...@gmail.com on 13 Jul 2011 at 10:44