It seems like they want some way to parameterize parts of the configuration with system properties:
“With Log4J 1, we were able to parameterize which appender to attach to the root logger by substituting the zookeeper.root.logger property with something like INFO, CONSOLE or INFO, ROLLINGFILE. It appears this is not as easily controlled in Log4J 2, where the configuration is more structured and switching appenders requires more changes in the configuration file.” https://issues.apache.org/jira/browse/ZOOKEEPER-2342?focusedCommentId=15081785&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15081785 https://svn.apache.org/repos/asf/zookeeper/trunk/conf/log4j.properties Do we have any way to achieve something similar in Log4j 2? On Aug 12, 2016 6:52 PM, "Mikael Ståldal" <[email protected]> wrote: > There seem to be quite some frustration in some other Apache projects > about migrating from Log4j 1. Especially around configration. Some seem to > consider dropping Log4j completely instead of going for Log4j 2. > > I have taken on Spark, Hadoop and Zookeeper; see links to their Jira > issues from LOG4J2-1473. I could need some help. >
