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 2012/10/13 19:44:03 UTC

[jira] [Closed] (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:all-tabpanel ]

Ralph Goers closed LOG4J2-9.
----------------------------

    Resolution: Fixed

Closing since the Configuration aspect is pretty solid.
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org