Also, a tool similar to this one: <http://logback.qos.ch/translator/> would be rather handy!
On 17 July 2014 16:53, Matt Sicker <boa...@gmail.com> wrote: > https://issues.apache.org/jira/browse/LOG4J2-635 > > Feel free to vote on this, contribute patches, etc. I've spent a little > bit of time working on a ConfigurationFactory for properties files, but it > quickly became a non-trivial task converting a flat map structure into a > tree. > > For what it's worth, I find the log4j.properties file confusing. I have no > idea how to configure log4j 1.2 using the properties file. I've always used > the XML format due to it being much easier. > > > On 17 July 2014 16:28, Mariano Gonzalez <mariano.l.gonza...@gmail.com> > wrote: > >> Hello all, >> >> I'm part of the development team of a popular middleware product that acts >> as an application container. I'm working in moving from log4j 1.2 to 2.0 >> for our next release. >> >> We noticed that most of our users use a log4j.properties file to configure >> logging in their applications. To make migration easier, I would like to >> build a custom ConfigurationFactory which is able to parse that >> .properties >> file and create the configuration. >> >> Do you already have something like that? Anyone had this migration issue >> already and has some tool for it? Is anyone considering adding something >> like this to the product? >> >> Thanks! >> > > > > -- > Matt Sicker <boa...@gmail.com> > -- Matt Sicker <boa...@gmail.com>
