Looking at the JCLOUDS-1xxx issues (September 2015 to present), our users reported 8 JDK 7 issues and 8 JDK 8 issues. You can repeat this analysis via:
for i in `seq 1400`; do echo $i; wget https://issues.apache.org/jira/si/jira.issueviews:issue-xml/JCLOUDS-$i/JCLOUDS-$i.xml; done grep -A1 '<environment>' JCLOUDS-* | grep -i -e jdk -e java | tr '\r' '\n' On Tue, Feb 20, 2018 at 11:33:52PM -0800, Andrew Gaul wrote: > To establish the current state, I believe that jclouds works with Java > 6-8 and 9 with --add-modules java.xml.bind and Guava 18-23, although I > will defer to you about the lack of 22+ support. Guava has proven to be > a painful dependency and one we should minimize going forward, even with > the stronger compatibility pledges from the Guava team. > > While supporting users with antique Java and Guava version has noble > intentions, I do not believe we have the development resources to > support all things for all people. Personally I prefer to support only > Java 8 and newer and Guava 21 and onwards, the first Guava to support > Java 8. However, several contributors championed more backwards > compatibility in the following mailing list threads: > > https://lists.apache.org/thread.html/1089e75e6be122024a3c1a45fdfd8c4c6545ce8df319a46c83831684@1401303438@%3Cuser.jclouds.apache.org%3E > https://lists.apache.org/thread.html/b8f2d9f55a3f8ebc07068dbe85cbef9dff0470b21ddbc89fa78601ac@1414426875@%3Cdev.jclouds.apache.org%3E > https://lists.apache.org/thread.html/2653bad70cbad009b54c612f02b4c6a09fd02dcd111c7319b9ed3b26@%3Cdev.jclouds.apache.org%3E > > I still loathe to touch the third rail of dependency versioning but the > pain of old software exceeds my interests and I believe deters users > with newer software and contributors. If someone wants to use or > support the older users please speak up and volunteer your time for this > Sisyphean task. > > [As a small suggestion, we can easily use reflection to call either > getHostText or getHost with older Guava.] > > On Tue, Feb 20, 2018 at 02:25:28PM -0500, William L. Thomson Jr. wrote: > > Per request posting here to start a discussion on moving past Guava 20. > > Please refer to the following. > > > > https://issues.apache.org/jira/browse/JCLOUDS-1333 > > https://github.com/jclouds/jclouds/pull/1180 > > > > TL;DR; The issues raised in PR 1180 are summarized as follows; > > > > - There are to many issues with trying to use Guava 21, skip > > that version. (see PR for issues) > > - To go to Guava 22+, requires moving to 1.8, as those jars > > are built for newer Java. I do not believe available for > > older. > > -There are API changes in 22+, getHostText replaced with > > getHost. Making it difficult to support older and newer Guava. > > > > Which means for JClouds to move forward with Guava, likely have to drop > > support for 1.7. That is mostly what needs to be discussed. > > > > Can JClouds drop 1.7, and move forward to 1.8+ only? > > > > May need to split code base and have a legacy version, and current. > > Like 2.0.x supports 1.7, and 2.1.x supports 1.8+. > > > > I feel there is no road forward for PR 1180, and will likely close as > > such. I can open a new PR with changes for Guava 22+. Which are > > considerably less than changes for 21. Which will cause issues with > > Guava 22+. Thus skipping Guava 21 entirely. > > > > FYI I have JClouds using Guava 24, and both built under Java 9, and > > soon Java 10. The changes are not much, and seems fine. But does drop > > legacy support. > > https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/dev-java/jclouds-core/jclouds-core-9999.ebuild#L34 > > > > Me personally I am past 1.8. But seems a fair amount are still running > > that version. It is still supported by most vendors. > > > > http://www.oracle.com/technetwork/java/eol-135779.html > > https://developer.ibm.com/javasdk/support/lifecycle/ > > https://access.redhat.com/articles/1299013 > > > > -- > > William L. Thomson Jr. > > > > -- > Andrew Gaul > http://gaul.org/ -- Andrew Gaul http://gaul.org/
JCLOUDS-247.xml: <environment>Ubuntu 13.04, Maven3, JDK7</environment> JCLOUDS-249.xml: <environment>OS X 10.8.4, Oracle Java 1.7.0_25</environment> JCLOUDS-498.xml: <environment>Tested on Windows 7 with Java 1.7.0_45</environment> JCLOUDS-519.xml: <environment>CentOS 6, JAVA Oracle JDK 7</environment> JCLOUDS-539.xml: <environment><a href='mailto:root@sonash3-00'>root@sonash3-00</a>:~/jclouds# javac -version<br/> JCLOUDS-539.xml-javac 1.7.0_51<br/> JCLOUDS-542.xml: <environment>jDK 1.7</environment> JCLOUDS-556.xml: <environment>jdk 1.7.0_45, jclouds 1.7.2</environment> JCLOUDS-569.xml-Oracle Java 1.8 JDK</environment> JCLOUDS-604.xml: <environment>$ java -version<br/> JCLOUDS-604.xml-java version &quot;1.7.0_21&quot;<br/> JCLOUDS-605.xml: <environment>$ java -version<br/> JCLOUDS-605.xml-java version &quot;1.7.0_21&quot;<br/> JCLOUDS-626.xml: <environment>Mac OS X 10.9.4, Oracle Java 1.7.0_55; RHEL 6.5, IBM Java </environment> JCLOUDS-677.xml: <environment>Windows 7, JDK 1.7.0</environment> JCLOUDS-703.xml: <environment>Java 1.8</environment> JCLOUDS-704.xml-JDK: 1.7<br/> JCLOUDS-776.xml: <environment>Windows 7, Chef Server 11.x, Java SDK 7</environment> JCLOUDS-798.xml: <environment>jdk 1.7, windows 7</environment> JCLOUDS-812.xml-Java 1.7</environment> JCLOUDS-840.xml: <environment>Mac OS X 10.9.5, Oracle JDK 1.8.0_25</environment> JCLOUDS-847.xml: <environment>JDK 1.7.0_55, 64bit, Windows 7<br/> JCLOUDS-881.xml: <environment>Google App Engine SDK 1.9.18; Java 1.8.0_05; Eclipse Luna; Windows 8.1 (could not replicate on same codebase running in Debian GNU/Linux; GAE 1.9.17; Java 1.7.0_65.)</environment> JCLOUDS-912.xml-java version &quot;1.7.0_76&quot;<br/> JCLOUDS-920.xml-Java version: java version &quot;1.7.0&quot;<br/> JCLOUDS-923.xml: <environment>Ubuntu 14.04 x64, OpenJDK 7, Rackspace cloud</environment> JCLOUDS-1009.xml-Java version: 1.7.0_51, vendor: Oracle Corporation<br/> JCLOUDS-1015.xml: <environment>Microsoft Windows (tested on 7 and 10), Java 7 and 8.</environment> JCLOUDS-1027.xml: <environment>Java 1.7 under Linux</environment> JCLOUDS-1116.xml: <environment>Windows 10 x64, Java 1.8.0_71 x64, Maven 3.3.9</environment> JCLOUDS-1144.xml: <environment>JDK 1.8</environment> JCLOUDS-1193.xml-java version &quot;1.8.0_102&quot;</environment> JCLOUDS-1205.xml: <environment>CentOS 6.8, OpenJDK 1.8.0.111-0.b15.el6_8</environment> JCLOUDS-1246.xml-Java - 1.7<br/> JCLOUDS-1248.xml: <environment>Java - 1.7<br/> JCLOUDS-1250.xml-Java 1.7<br/> JCLOUDS-1251.xml-Java 1.7</environment> JCLOUDS-1279.xml: <environment>RHEL 7.2, Java 1.7</environment> JCLOUDS-1292.xml-Java 1.8.0_112</environment> JCLOUDS-1293.xml: <environment>java 1.8.0_112<br/> JCLOUDS-1297.xml: <environment>Java 8</environment> JCLOUDS-1320.xml: <environment>Java 8</environment>
