avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject excalibur-logger compilation problems
Date Fri, 11 Oct 2002 12:24:55 GMT

Log4j has just recently merged its 1.2 CVS branch with its main (1.3)
branch. Apparently this is causing excalibur-logger from compiling
properly.

The reason the code fails to compile is because as of log4j 1.2 the
Category.getDefaultHierarchy method returns a LoggerRepository instead
of a Hierarchy. The Category.getDefaultHierarchy() method was also
deprecated in log4j 1.2. This change occurred over 13 months ago. So I
fail to understand is why this problem surfaces now. The merge between
the 1.2 branch and the trunk barely influenced the Category
class. Indeed, the diff between Category.java version 1.68 (at the
base of the 1_2 branch) and 1.69 (the most recent version) has no
bearing to the compilation problem in excalibur-logger.

What am I missing? Did excalibur-logger ever work with log4j 1.2?

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message