Log4j2 has already had a couple of releases. Either you need the new features and support or you do not. Log4j 1 is unlikely to see another release.
Gary <div>-------- Original message --------</div><div>From: Piers Uso Walter <[email protected]> </div><div>Date:12/01/2014 03:27 (GMT-05:00) </div><div>To: Log4J Developers List <[email protected]> </div><div>Cc: </div><div>Subject: Re: Java 7? </div><div> </div>We still have quite a few projects that depend on Java 6 and were just about to start migrating these from log4j to log4j2. I guess we’ll have to wait and see how this discussion plays out… With kind regards Piers Uso Walter <[email protected]> Am 01.12.2014 um 07:56 schrieb Gary Gregory <[email protected]>: Just to play devil's advocate... I'm not so sure on the laggard view. If I start a new project today, it is a Java 8 project or maybe a java 7 project if some kit breaks on 8. For my major existing project that recently moved from java 6 to 7, I gave up upgrading from log4j 1 to 2 because we depend on to many log4j guts (configuration and custom appender). So for me, java 7 is the min and some folks in our company are starting to discuss making java 8 the min just mitigate some real or perceived security issues. Gary -------- Original message -------- From: Ralph Goers <[email protected]> Date:12/01/2014 01:13 (GMT-05:00) To: Log4J Developers List <[email protected]> Cc: Subject: Re: Java 7? We have had this discussion before. There are some components that should be leaders and some that should be laggards when it comes to upgrading. My opinion is that Log4j needs to be at the tail end in terms of dropping support for older Java versions. Ralph On Nov 30, 2014, at 11:05 PM, Gary Gregory <[email protected]> wrote: Hm, one of those blog shows Java 7 ~ 80 % and Java 6 at ~20 %. That fits the general 80/20 rule for me ;-) Gary On Mon, Dec 1, 2014 at 12:58 AM, Ralph Goers <[email protected]> wrote: Or, I guess, when one of these surveys shows Java 6 is down below 10%. Neither of these is extremely current, but it is interesting to note that the second showed Java 6’s usage actually increase over the last several months. I can’t imagine why that would be. http://adtmag.com/blogs/watersworks/2014/05/2014-java-survey.aspx http://blog.jelastic.com/2014/05/20/software-stacks-market-share-april-2014/ FWIW, I am still using Java 6 at work for some things so I have no interest in not being able to use Log4j 2 in them. They should all be upgraded in the next few months. Ralph On Nov 30, 2014, at 10:32 PM, Ralph Goers <[email protected]> wrote: November 2015. Ralph On Nov 30, 2014, at 10:12 PM, Gary Gregory <[email protected]> wrote: I just had to do some refactoring to account for not being able to use a Java 7 multi-catch. I would be OK to release 2.2 ASAP and then make Java 7 the minimum to take advantage to Java 7 features like multi-catch and try-with resources. Thoughts? Gary -- E-Mail: [email protected] | [email protected] 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 -- E-Mail: [email protected] | [email protected] 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
