On Tue, Oct 31, 2017 at 6:18 AM, Nick Couchman <[email protected]> wrote:
> This has come up in a couple of PRs, so I wanted to throw this out for > discussion. Currently most of the Guacamole client code is targeted at > Java 1.6 compatibility (via entries in the pom.xml files). There have been > a couple of instances where that was a minor inconvenience, though not all > that problematic. However, I just did a PR for migrating the LDAP > authentication extension from the legacy Novell LDAP API over to Apache's > Directory LDAP API, and that (apparently) requires Java 1.7 or later. > > For the LDAP extension it's easy to just require that to be at 1.7 and > allow the rest to be at 1.6, but the question becomes: is there any reason > *not* to bump the requirement/target/compatibility for Java to 1.7 or even > 1.8 across the board? The last publicly-available 1.6 version was in 2015 > (U91), with 1.8 starting in 2014 and 1.9 starting this year. Seems like > it's probably pretty safe to move beyond 1.6? > > Thoughts? > > I would be happy to see everything bumped up to Java 7. I don't think we can safely bump all the way to Java 8 across the board, as I believe it's still relatively widely used and supported, but I'd be interested to hear what others think here. - Mike
