Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
empire-db-2.0.6-incubating
-
None
Description
Our xml configuration system allows log4j configuration. This however makes empire-db dependent on log4j, even if we use commons logging everywhere else. As this log4j xml inside config.xml brings no real added value and most people have their own log4j.xml anyway. I suggest we remove log4j related stuff. We need to focus on being a library and not a framework.
eg: In my own projects I prefer to use slf4j with logback as implementation. Therefore I can then exclude commons logging and use jcl-over-slf4j instead. So I don't want log4j on the classpath