Allow users to configure Tyrex to output its messages to Log4J.
As a quick n dirty patch to restore usage of log4j rather than commons-logging apply the following diff:
diff -w -b Category.java src/main/tyrex/util/logging/Category.java 53,55c53,54 < < import org.apache.commons.logging.Log; < import org.apache.commons.logging.LogFactory; --- > // import org.apache.commons.logging.Log; > // import org.apache.commons.logging.LogFactory; 67c66,67 < private Log mLog; --- > // private Log mLog; > private org.apache.log4j.Category mLog; 83c83,84 < mLog = LogFactory.getLog(pName); --- > mLog = org.apache.log4j.Category.getInstance (mName); > // mLog = LogFactory.getLog(pName);
Log in to post a comment.
As a quick n dirty patch to restore usage of log4j rather than commons-logging apply the following diff:
diff -w -b Category.java src/main/tyrex/util/logging/Category.java
53,55c53,54
<
< import org.apache.commons.logging.Log;
< import org.apache.commons.logging.LogFactory;
---
> // import org.apache.commons.logging.Log;
> // import org.apache.commons.logging.LogFactory;
67c66,67
< private Log mLog;
---
> // private Log mLog;
> private org.apache.log4j.Category mLog;
83c83,84
< mLog = LogFactory.getLog(pName);
---
> mLog = org.apache.log4j.Category.getInstance (mName);
> // mLog = LogFactory.getLog(pName);