Allow users of ForwardingFileManager to specify if the delegate file manager should also be closed.
This fixes a use-after-close bug in TestOriginatingElements, where the system file manager and wrapping memory file manager have different, nested, lifetimes resulting in an early call to close the system file manager when the wrapper is closed, causing subsequent legitimate use of the system file manager to fail. This wasn't noticed before now since the system file manager was using the singleton JRT file-system in which "close" does nothing. Now it's using a properly scoped instance of the JRT file-system which can be closed. This fix could also probable go straight into mainline as a clone since it won't break anything there. ------------- Commit messages: - Allow callers to decide if delgate file manager should be closed Changes: https://git.openjdk.org/valhalla/pull/1810/files Webrev: https://webrevs.openjdk.org/?repo=valhalla&pr=1810&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8373825 Stats: 57 lines in 3 files changed: 25 ins; 26 del; 6 mod Patch: https://git.openjdk.org/valhalla/pull/1810.diff Fetch: git fetch https://git.openjdk.org/valhalla.git pull/1810/head:pull/1810 PR: https://git.openjdk.org/valhalla/pull/1810
