You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2010/04/15 10:04:50 UTC
[jira] Created: (EMPIREDB-77) Get rid of the Log4J compile-time
dependency
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
[jira] Updated: (EMPIREDB-77) Get rid of the Log4J compile-time
dependency
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-77:
------------------------------------------
Affects Version/s: empire-db-2.0.6-incubating
Fix Version/s: (was: empire-db-2.0.7-incubating )
empire-db-2.0.8-incubating
> 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.0.8-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.
[jira] Updated: (EMPIREDB-77) Get rid of the Log4J compile-time
dependency
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-77:
------------------------------------------
Fix Version/s: empire-db-2.0.7-incubating
Affects Version/s: (was: empire-db-2.0.7-incubating )
> 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
> Reporter: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.0.7-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.