Log4j 1.x stuck with JDK 1.2 for many years for a reason. Although public support for Java 6 ended in 2013, Oracle’s site [1] says Premier support is available until Dec 2015 and extended support is available until Dec 2018. Java 7’s extended support runs through 2022. So just because the “free” version will be at “end of life” doesn’t necessarily mean everyone will stop using it.
That said, I think we should have a coherent policy. For example, we could plan to upgrade our minimum version whenever Premier support ends (Java 6 until Dec 2015, Java 7 until July 2019, etc). I also wouldn’t want to jump from version 2.x to 3.x just because we changed the minimum JDK version. At the same time I think it should be clear to users that they can’t just upgrade from 2.2 to 2.3. That may mean we would want to use 4 digit version numbers and only go to 2.1.0.0 when we switch the JDK. I should also state that I have no problem if some of our add-on modules require a different JDK version. I also think we could do things like make things like Date formatting be pluggable so that if you are running on JDK 8 you can use it instead of whatever core normally provides. Ralph [1] http://www.oracle.com/technetwork/java/eol-135779.html On Sep 13, 2014, at 2:16 PM, Gary Gregory <[email protected]> wrote: > FYI > > -------- Original message -------- > From: Stephen Connolly > Date:09/13/2014 07:56 (GMT-05:00) > To: Maven Developers List > Subject: Java 7 EOS now set for April 2015 > > http://mail.openjdk.java.net/pipermail/jdk7u-dev/2014-April/008910.html > > Wondering if we should start thinking about upping to Java 7 as our minimum > next year ;-) > > Sent from my iPad
