We have this section in the admin doc that talks about the system requirements:
https://zookeeper.apache.org/doc/r3.5.3-beta/zookeeperAdmin.html#sc_requiredSoftware <https://zookeeper.apache.org/doc/r3.5.3-beta/zookeeperAdmin.html#sc_requiredSoftware> If we change, then we have to update that section. Specifically about client and server, I'd think that there is no problem with requiring Java 8 on the server. The potential concern is with the client as it affects applications that build against it. It would be best to not force applications to upgrade themselves. Looking at the compatibility guide for Java 8: http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html <http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html> The risk is that an application is strictly using Java 7 because of some incompatibility listed in that guide, in which case, it wouldn't be able to compile the ZK client assuming we get it to use some Java 8 construct. One option is that we raise the requirement to Java 8, but we do no really introduce anything that breaks compatibility for the next version. Users should take this as a warning that they need to migrate to Java 8. I'm not sure this makes the situation any better, though. Another option is that we set a release to be the one in which we migrate and let everyone know that they need to migrate. -Flavio > On 16 Feb 2018, at 12:05, Andor Molnar <an...@cloudera.com> wrote: > > Hi all, > > I think it would be nice to draw a line at branch-3.5 and target Java > version 8 onwards. It seems to be a good opportunity for the upgrade before > we release a stable version of 3.5. > > The benefit would be the ability to use new features of Java 8 in the code: > > Do think it's feasible? > > Regards, > Andor
