From 36c73c13e21915b66bedd77df9a7adf596a60464 Mon Sep 17 00:00:00 2001
From: Simon Kitching <skitching@apache.org>
Date: Sat, 20 Sep 2008 16:33:51 +0000
Subject: [PATCH] LOGGING-127: Fix issue introduced in LOGGING-126 - use
 setUseCache, not setDefaultUseCache Thanks to Christopher Sahnwaldt for the
 report.

git-svn-id: https://svn.apache.org/repos/asf/commons/proper/logging/trunk@697387 13f79535-47bb-0310-9956-ffa450edef68
---
 src/java/org/apache/commons/logging/LogFactory.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/java/org/apache/commons/logging/LogFactory.java b/src/java/org/apache/commons/logging/LogFactory.java
index 2a15a9c..342c260 100644
--- a/src/java/org/apache/commons/logging/LogFactory.java
+++ b/src/java/org/apache/commons/logging/LogFactory.java
@@ -1427,7 +1427,7 @@ public abstract class LogFactory {
                         // default behaviour of java is to cache file handles, and
                         // this "locks" files, preventing hot-redeploy on windows.
                         URLConnection connection = url.openConnection();
-                        connection.setDefaultUseCaches(false);
+                        connection.setUseCaches(false);
                         stream = connection.getInputStream();
                         if (stream != null) {
                             Properties props = new Properties();