[
https://issues.apache.org/jira/browse/CONFIGURATION-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211957#comment-17211957
]
Rob Spoor commented on CONFIGURATION-794:
-----------------------------------------
Do you mean adding a flag somewhere to disable the caching, with caching
enabled by default? Because I ran the failing test, and it succeeded with the
quick fix applied. I didn't try any of the other tests so it's possible there
could be failures, although I think it isn't likely.
I think a flag would make sense. In most cases, there is no need to replace JAR
files while the JVM is active. I've never had this problem when using Commons
Configuration inside JEE applications on Windows; EARs could be redeployed
without any issues. If people need the option to have JAR files hot-swappable,
then they could just set the flag, accepting the (possible) performance hit.
> Unclosed file handle when reading config from JAR file URL
> ----------------------------------------------------------
>
> Key: CONFIGURATION-794
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-794
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Robin Jansohn
> Priority: Major
>
> We read a properties file which is included in a JAR file. Unfortunately we
> cannot find any method to close the opened file handle after reading the
> properties.
> This currently means that the JAR file can only be deleted after the JVM
> shuts down. I'll open a PR which shows the behavior.
> We currently run our code mostly on Windows systems and Oracle JDK8.
> PR: https://github.com/apache/commons-configuration/pull/76
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
