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] Commented: (EMPIREDB-77) Get rid of the Log4J compile-time dependency
Date Mon, 24 Jan 2011 20:36:43 GMT

    [ https://issues.apache.org/jira/browse/EMPIREDB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985968#action_12985968
] 

Francis De Brabandere commented on EMPIREDB-77:
-----------------------------------------------

This issue is not so important any more in my eyes, because the xml config was split off.

Do we plainly want to remove the log4j settings in out xml or make that pluggable somehow.

> 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.6-incubating
>            Reporter: Francis De Brabandere
>            Priority: Minor
>             Fix For: empire-db-2.1.0-incubating
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message