Janne Jalkanen wrote:
I've come out before against adding Yet Another Logging Package (YALP) to
our set of jar files, and while I'd still really prefer to avoid doing
that I thought I would offer support for going with java.util.logging, in
that if JSPWiki relied entirely on it I'd be willing (and relatively
happy) to go to the trouble of moving my own code over to that for the
same reasons as you state: I'd like to remove unnecessary dependencies
and reduce the overall weight of my installations. The redundancies of
the current situation are likewise frustrating.
Unfortunately, java.util.logging does not reduce our dependencies at
all. Some external jars that we have require commons logging, some
require log4j, so we can't get rid of those.
Moving to jabsorb in preference of jsonrpc lib means that we have to
*add* another set of logging libraries, namely slf4j.
java.util.logging does not really help the situation at all (and in
fact, makes it worse, since j.u.l does not support multiple logging
configurations per jvm, which is pretty much a showstopper for my own
installations, for example.)
Janne,
Yes, in reading further along in the thread I have come to understand
this situation. Yuck. I looked over the j.u.l documentation to see if
there was perhaps some loophole but if there is it's not obvious; seems
there's one LogManager per JVM.
Sorry I have little else to add...
Murray
...........................................................................
Murray Altheim <murray07 at altheim.com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
