Hi Simon!
Why wouldnt you create this wrapper library under the umbrella of
commns-logging?
Different commons-logging libraries using static linking instead of the
dynamic behaviour.
Say: commons-logging-log4j, commons-logging-jdklogger
That way we still can use the well known LogFactory and every other
project will benifit from this too.
One can replace the logging implementation used just by replacing the jar.
I think it isnt that a good idea if every project comes with its own
wrapper library. In the worst case this will double the number of
libraries used - even more logging hassle.
just my 2ct.
Mario
