Janne Jalkanen (JIRA) wrote:
[ https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642547#action_12642547 ]
Janne Jalkanen commented on JSPWIKI-376:
----------------------------------------
Yeah, that's what you get when you have multiple logging packages, all
incompatible, and all changing and/or abandoned, with the one that is
a default is nigh useless.
A lot of projects (like Stripes) therefore use their own logging
abstraction so that people can rewrite it if they want to.
Another possibility might be to switch to java.util.logging and simply
get rid of all logging libraries. But no, we can't do it because we
have library dependencies to all sorts of strange logging libraries...
It's extremely frustrating. With all my other projects, I'm just using
the java builtin logging. It may suck, but at least *I* won't be the
one bringing in a dumb dependency to a logging library.
Hi Janne,
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.
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
