Paul Smith wrote:
It would really seem that there has been no attempt along these
lines to date. logj4 1.3 is currently only an alpha so issues are
to be expected at this point, *but* I believe binary compatibility
and removal of Category and Priority are mutually exclusive. [I'd
be happy to be proven wrong on this.] The best one could seemingly
achieve is introduction of a log4j 1.2.xx release which binaries
compiled agianst will also work with log4j 1.3. If binaries built
against any currently existing 1.2.x release are to be supported
then we have to keep Category and Priority around as I see it.
I'm no binary-compatibility expert, but I can't see how we can
maintain it while dropping Category. I'm beginning to think that we
(log4j community) are very much as Elias pointed out. Stuck with
marking it as deprecated, but 'forever' keeping it. Putting aside
technical aspects of keeping things clean, all we would do is
alienate the community. There's no point having a rockin' API if
everyone has been burnt by it and moved on to other things.
Actually I believe I may have been a bit hasty in jumping to the
conclusion that Category cannot be removed. I do not have any cases
wherein code written against Logger and Level -- as per what are now
fairly longstanding 1.3 compatibility guidelines -- is not binary
compatible with 1.3 when compiled against 1.2. There may or may not be
any such cases. The other question is how many current versions of open
source libraries, etc, still use Category directly. As one related
example, the RootLogger class only came into existence in a rather
recent 1.2.x release so prior to that there was no choice but to use
RootCategory for such things.
I believe the examples showing the need for Priority to maintain binary
compatibility are fairly clear and unfortunately affect some fairly
frequently used methods of Logger. In our case, these methods affect
dozens of classes spread throughout numerous modules, whereas the
various source-code changes necessary for 1.3 were limited to relative
few files in a few modules which generally were making more elaborate
usage of log4j than what might be consider the 80-90% case of simple
Logger/Level usage.
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
