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 2016/08/17 14:14:20 UTC
[jira] [Commented] (LOG4J2-1525) Convert Log4j 1 log4j.properties
into equvivalent Log4j 2 config file
[ https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424586#comment-15424586 ]
Ralph Goers commented on LOG4J2-1525:
-------------------------------------
If a meta-data file can be provided that maps Log4j 1 components to their Log4j 2 counterparts this might be possible. In fact, using that same meta data it might be possible to build a Log4j 2 wrapper around Log4j 1 components.
> Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file
> ---------------------------------------------------------------------
>
> Key: LOG4J2-1525
> URL: https://issues.apache.org/jira/browse/LOG4J2-1525
> Project: Log4j 2
> Issue Type: Sub-task
> Components: Configurators
> Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org