I would be okay with that, but I'd like to print out a warning message and the equivalent Log4j2 configuration to the console without any option to switch this off.
Sent from my iPhone > On 2016/08/15, at 17:48, Mikael Ståldal <mikael.stal...@magine.com> wrote: > > Any objections to reopening LOG4J2-63, and targeting it for 2.7? > >> On Sat, Aug 13, 2016 at 1:18 PM, Mikael Ståldal <mikael.stal...@magine.com> >> wrote: >> Seems to be in https://issues.apache.org/jira/browse/LOG4J2-63 >> >> It is currently marked as Won’t Fix. Should we reopen this issue? >> >> >>> On Aug 13, 2016 1:04 PM, "Mikael Ståldal" <mikael.stal...@magine.com> wrote: >>> Do we have a JIRA issue to track this? >>> >>> >>>> On Aug 12, 2016 7:06 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote: >>>> Please consider expanding what I started here >>>> org.apache.log4j.config.Log4j1ConfigurationFactory >>>> >>>> Gary >>>> >>>>> On Fri, Aug 12, 2016 at 9:52 AM, Mikael Ståldal >>>>> <mikael.stal...@magine.com> 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. >>>>> >>>> >>>> >>>> >>>> -- >>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>>> Java Persistence with Hibernate, Second Edition >>>> JUnit in Action, Second Edition >>>> Spring Batch in Action >>>> Blog: http://garygregory.wordpress.com >>>> Home: http://garygregory.com/ >>>> Tweet! http://twitter.com/GaryGregory > > > > -- > > > Mikael Ståldal > Senior software developer > > Magine TV > mikael.stal...@magine.com > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this message. > If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply email. >
