Bug 35893 - Loader.getResource has broken compatibility with Log4J 1.1
Summary: Loader.getResource has broken compatibility with Log4J 1.1
Status: RESOLVED FIXED
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2
Hardware: Other other
: P2 major
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-27 12:50 UTC by Niall Smart
Modified: 2005-07-29 04:25 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Niall Smart 2005-07-27 12:50:37 UTC
The signature of org.apache.log4j.helpers.Loader.getResource() has changed
between 1.1 and 1.2.   In 1.1, it is:

    public static URL getResource(String resource, Class clazz) 

In 1.2, it changed to:

    public static URL getResource(String resource)

We are using 3rd party software that relies on the first method signature, so we
see a NoSuchMethodError when using 1.2.   We would like to updated to 1.2 to
make use of the MDC class.   Can a backwards compatibility method be added to
this class?
Comment 1 Curt Arnold 2005-07-27 18:24:58 UTC
Compatibility method added to both v1_2-branch and HEAD.  Excellent timing since a 1.2 maintenance 
release (1.2.12) is imminent.  Please report any other issues as quickly as possible since no additional 
work on the v1_2-branch is currently planned after the release.

To check out the v1_2-branch source

cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic co -r v1_2-branch logging-log4j

The HEAD as many known compatibility issues with 1.2 which we are working to resolve, so it is highly 
unlikely that it could act as a drop-in for log4j 1.1 at this time.
Comment 2 Niall Smart 2005-07-27 18:26:50 UTC
If there is a release candidate available we will test it for any other compat
issues?
Comment 3 Mark Womack 2005-07-27 18:31:23 UTC
I will be building a 1.2.12rc1 build later tonight.  Watch the log4j-dev email 
list for details.
Comment 4 Niall Smart 2005-07-29 12:25:41 UTC
1.2.12rc1 has fixed the problem for us - thanks very much!