CALL FOR: Removing `support' for log4j 1.1, to ease transition from 1.5 to 1.6 installations and to have one package less to maintain.
DESCRIPTION Currently in the code there are two packages devoted to the log4j implementation of the logging system: org.mmbase.util.logging.log4j and org.mmbase.util.logging.log4j2 the 'log4j' package contains code for log4j version 1.1 and the log4j2 package contains the code for log4j version 1.2. Due to some changes in log4j itself it unfortunately could not be the same code. In the build-process one of the package is chosen to be compiled, and the other one is not build. Since a month or three the 'default' in CVS HEAD is 'log4j2', and this worked more or less. Today I updated the log4j2 implemention and the support is more complete now. The configuration file e.g. does not need the reference to the 'logger' implementation any more and can use 'logger' and 'level' tags in stead of the (by log4j) obsoleted 'category' and 'priority' concepts. A lot of 1.5 installations will suffer anyway when they go from log4j 1.1 to log4j 1.2 because of this unfortunate 'entity logger' issue which I reported about in this list (meaning that a entity 'logger' in a log4j 1.2 XML configuration file is ill chosen now (bad luck, it wasn't in 1.1)). Another thing which had to be changed in 1.5 config files is the the package name 'log4j -> log4j2', and to avoid this, and to clean up de source code I came up with this hack: Lets remove the current 'log4j' package and rename the current 'log4j2' package to 'log4j', thus effectively dropping all support for log4j 1.1 (the necessary code will not even be available in the source distro). 'log4j2' is a stupid package name anyway. To support easier transition from 1.5 isntallations to 1.6 installations in log4j2 I today also added a (deprecated :-) 'Log4jPriority' class which simply copies the more logical 'Log4jLevel' (So then the 'logger' entity of 1.5 config files has to be removed or renamed only) Besides this issue with the 'logger' entity old configuration files will remain working, but they can be improved (with logger and level tags), and the default example configuration will of course be like this (as in CVS now). Note that it is MMBase policy to depend as much as possible on the latest stable version of 'external' libraries. LINKS: thread Jul 24 10:03 Michiel Meeuwissen ( 18) log4j 1.2.4 of this list: http://www.mmbase.org/archive/developers/msg05041.html START OF CALL: 2002-10-21 22:30 END OF CALL: 2002-10-24 22:30 [_] +1 (YEA) [_] +0 (ABSTAIN ) [_] -1 (NAY), because : [_] VETO, because: Michiel -- % Michiel Meeuwissen % [EMAIL PROTECTED] % http://www.purl.org/NET/mihxil/ % Vidu ankaux: http://www.uea.org/katalogo
