You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2010/05/15 08:53:41 UTC
[jira] Commented: (LOG4J2-9) log4j 2.0 should leverage existing
(preferably ASF) configuration frameworks
[ https://issues.apache.org/jira/browse/LOG4J2-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867816#action_12867816 ]
Ralph Goers commented on LOG4J2-9:
----------------------------------
In my experimental branch the configuration is pluggable. I investigated using other frameworks but adding a dependency really isn't worth the cost (and risk that the framework will somehow create a circularity problem). In the end the configuration I implemented is extremely simple.
> log4j 2.0 should leverage existing (preferably ASF) configuration frameworks
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-9
> URL: https://issues.apache.org/jira/browse/LOG4J2-9
> Project: Log4j 2
> Issue Type: Wish
> Components: Configurators
> Reporter: Curt Arnold
>
> log4j 2.0 should avoid implementing its own configuration framework in preference to being compatible with commonly used configuration frameworks and services. Compatibility with existing log4j 1.2 configuration files might be accomplished by XSLT transforms that convert the legacy format into the equivalent with the selected configuration framework. log4j 2.0 should be readily configurable with JMX and a JMX centric design for configuration may be desirable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org