[
https://issues.apache.org/jira/browse/LOG4J2-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383591#comment-15383591
]
Ralph Goers commented on LOG4J2-1436:
-------------------------------------
I would not be thrilled with this. At least by requiring a tool that converts
the old configuration to the new we can inject comments about things that don't
have a direct translation. By just auto-magically using the log4j 1
configuration we would be encouraging people to go on using that format
indefinitely.
> Log4j2 migration tools
> ----------------------
>
> Key: LOG4J2-1436
> URL: https://issues.apache.org/jira/browse/LOG4J2-1436
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators, Documentation, log4j 1.2 emulation
> Reporter: Remko Popma
> Fix For: 2.7
>
>
> TODO verify the status of the below projects and link to them from the site:
> http://log4j-props2xml.appspot.com/
> https://github.com/jroyals/log4j-properties-converter/
> https://github.com/mulesoft-labs/log4j2-migrator
> Also, consider adding separate pages for
> * Migrating to Log4j 2 from Logback
> * Migrating to Log4j 2 from JUL
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
