We've updated our CI matrix to include Java 10 and everything works except for the aforementioned OSGi testing issues.
The framework we use does not support JDK 10, and since we are using a really old version for JDK6 support. I opened up to look into this further in the future.

I also encountered a slight issue with our use of byteman in our tests which I was able to work around. See this pr for more info.

I removed Java 9 from the description as it is already no longer supported. It's pretty likely that if JDK 10 works, JDK 9 is likely to work, but we don't want to add another variable to our test matrix if we can avoid it.

I ran our CI with Java 9 and Java 10, and for the most part everything worked. The only thing that has given me issues is our OSGi tests, which may require some simple packaging updates to work with j9 and j10. Will have a more formal PR to update our CI to run with Java9 and Java 10 soon.

TL;DR I think we should focus on Java 8 for now and get prepared for the next LTS, Java 11. By "get prepared" I mean start explicitly testing the driver with the latest Java 10 (Java 9 is worthless imo), exercising both the classpath and the modulepath.

, Agreed. I think in the context of this ticket, it would be good just to make sure that there aren't any issues with the driver with Java 9 / 10 so we can say they are "Supported". In terms of supporting JDK specific features (like JPMS) I think it would be good to to track that work separately. If everything works well, I think it's just a matter of making sure our CI suite passes with Java 9 and 10.

Some food for thought:

1. http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.html

2. http://blog.joda.org/2018/03/jpms-negative-benefits.html

TL;DR I think we should focus on Java 8 for now and get prepared for the next LTS, Java 11. By "get prepared" I mean start explicitly testing the driver with the latest Java 10 (Java 9 is worthless imo), exercising both the classpath and the modulepath.