Hi,
I read up a bit on commons-logging and the commons-logging.properties
file. Switching the 2.3 code base to use this, would mean to drop the
explicit factory setting in Turbine.java, trust commons-logging to
find log4j correctly (which should be no big deal) and allow the users
to change their logging settings by adding a
commons-logging.properties file to the class path.
However, we should document this change and advise people to use a
commons-logging.properties file even if they plan on using only Log4j.
For obvious reasons it wouldn't make much sense to add such a file to
the turbine.jar. :-)
Another thing: Would it make sense to not initialize log4j if no
log4j.file property is found in the TR.props? Currently we default to
WEB-INF/conf/Log4j.properties.
Opinions?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
