[logback-dev] [JIRA] Resolved: (LBCORE-105) config files found in jar file lock the jar file
Ceki Gulcu (JIRA)
noreply-jira at qos.ch
Wed Jul 8 10:32:10 CEST 2009
[ http://jira.qos.ch/browse/LBCORE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ceki Gulcu resolved LBCORE-105.
-------------------------------
Fix Version/s: 0.9.16
Resolution: Fixed
Fixed in revision 2321.
> config files found in jar file lock the jar file
> ------------------------------------------------
>
> Key: LBCORE-105
> URL: http://jira.qos.ch/browse/LBCORE-105
> Project: logback-core
> Issue Type: Bug
> Components: Joran
> Affects Versions: 0.9.15
> Reporter: Ceki Gulcu
> Assignee: Ceki Gulcu
> Fix For: 0.9.16
>
>
> When a config file is obtained from within a jar file, the jar file is locked. This causes trouble when the application needs to be reloaded. See also bug #47465 in log4j. The solution is to set the setDefaultUseCaches to false when opening the url connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the logback-dev
mailing list