[
https://issues.apache.org/jira/browse/LOG4J2-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383460#comment-15383460
]
Remko Popma commented on LOG4J2-1436:
-------------------------------------
Nice! Direct support for the old format would make migration pretty painless...
It may be good to spit out a warning, or even better, print out the equivalent
Log4j 2 configuration to STDERR.
Does Log4j 2 use this configuration factory automatically when the old
configuration file naming convention (log4j.properties, log4j.xml) is used?
Is there a way to tell Log4j 2 to use this configuration factory for config
files that do not follow this naming convention?
> 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: [email protected]
For additional commands, e-mail: [email protected]
