While this may provide some benefits and be more flexible, it would
require that in every single instance of our use of JSPWiki (which
now reaches into three or four related projects) we would then have
two logging systems. Log4J, whatever its issues, is still by far the
most widely used Java-based logging package (so far as I know). It's
functional and works well. It is widely understood by our programmers
and contractors.
We have no issue with log4j in any of our other projects (where it
is used very widely), don't have any problems with it "playing well
with other applications", and newness or coolness really doesn't
enter into the decision-making process if that's the motivation.
I would much prefer that we stay with log4j, as this is for myself
only an added complexity, an added redundancy, with little benefit.
Mmmm... I suspect you didn't read SLF4J documentation, which I highly
recommend.
It is a front-end against several logging systems - and will work
together seamlessly with log4j as well. If log4j is your choice, the
change should be quite invisible for you (with the exception that
configuration *might* need to move to a separate file - which isn't
necessarily a bad thing, since our configuration is already somewhat
bloated). If it's not, then JSPWiki unfortunately at the moment
cannot give you a choice for your logging system. Considering that
the log4j issue with some containers seems to pop up every now and
then, I'd say that this is a low-hanging fruit which we can solve
rather easily.
Also, I *highly* recommend that you add to the JIRA instead of
posting to the mailing list. In a few months when the issue is
discussed again, it is unlikely that people will remember your
comments from the mailing list. :-)
/Janne
