Github user jmuehlner commented on a diff in the pull request:
https://github.com/apache/guacamole-client/pull/319#discussion_r220419865
--- Diff:
extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-base/pom.xml ---
@@ -109,33 +109,33 @@
<dependency>
<groupId>org.mybatis</groupId>
<artifactId>mybatis</artifactId>
- <version>3.2.8</version>
+ <version>3.4.6</version>
--- End diff --
On that note, public updates for Java 1.6 ended in 2013, and public updates
for 1.7 ended in 2015.
I think maybe it's time to reevaluate our reasons for sticking to 1.6. It's
certainly end of life at this point, and upgrading to 1.8 would help us have to
worry less about things like this. Are there really a lot of users running
Guacamole in environments where the highest available Java version is 1.6?
As far as Mybatis 3.46 goes, I had a look at the project POM and the docs,
and it's actually not obvious to me how to tell if this supports 1.6 without
just building the whole thing and attempting to run it in a 1.6 environment.
Maybe we shouldn't care though...
---
