JClouds won't be supporting Java 6 starting with next release (2.0.0) (see
the commit [1] and the PR that merged it [2]). Given their release history
so far it seems plausible that we can expect the new version beginning of
next year.
Seems like a good time to discuss what our plans for Java 6 should be:
1) Try to support Java 6 as long as possible, sticking to jclouds-0.8.0?
According to the Oracle's site Java 6 doesn't receive public
updates since Feb 2013. Commercial support is still ongoing (see [3]).
IBM's Java 6 is still supported until Sep 2017 (see [4]).
2) Migrate to jclouds-2.0.0 as soon as it is released, communicating a
roadmap for deprecating Java 6 to our users?
3) Support both JClouds versions in parallel, targeting Java 6 in the
meantime?
Whatever we choose looks like we will get a rough idea how long we will
stick with Java 6 which we should explicitly document on the website.
The Java 8 support is a related topic. Currently we can run on it, but the
project doesn't compile due to the eclipse-groovy-compiler not supporting
Java 8. My understanding is that Java 8 support won't be included in the 1.8
compiler version which we currently use. We can either port the existing
Groovy files to the latest compiler or convert them to Java.
What are your thoughts?
Best,
Svet.
[1]
https://github.com/andrewgaul/jclouds/commit/344ebfd2fa30954eb5c9aab5f2c9343
0d00905ca
[2] https://github.com/jclouds/jclouds/pull/426
[3] http://www.oracle.com/technetwork/java/eol-135779.html
[4] https://www.ibm.com/developerworks/java/jdk/lifecycle/
