empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] Created: (EMPIREDB-77) Get rid of the Log4J compile-time dependency
Date Thu, 15 Apr 2010 08:04:50 GMT
Get rid of the Log4J compile-time dependency
--------------------------------------------

                 Key: EMPIREDB-77
                 URL: https://issues.apache.org/jira/browse/EMPIREDB-77
             Project: Empire-DB
          Issue Type: Improvement
          Components: Core
    Affects Versions: empire-db-2.0.7-incubating 
            Reporter: Francis De Brabandere
            Priority: Minor


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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message