Support Oracle JDK9 EA

[gsmet]

Hi,

I'm working on having a Travis based build for Hibernate Search and we are willing to test Search against JDK9 EA to provide feedback to the JDK team.

The JDK9 is installable through the apt addons and the oracle-java9-installer package but the JDK switcher does not support it atm:

$ jdk_switcher use oraclejdk9

Sorry, but JDK 'oraclejdk9' is not known.

The command "jdk_switcher use oraclejdk9" failed and exited with 1 during .

Would it be possible to support it soon?

Thanks.

Guillaume

[gildegoma]

The jdk_switcher update and the JDK9 EA installation have already been prepared (see travis-ci/travis-cookbooks#587).

This is however not "production ready" at all (e.g. the jdk9 project is still in an "unstable" phase, the webupd8 apt package is not complete yet, etc). See also http://openjdk.java.net/projects/jdk9/ for the own OpenJDK9 schedule.

But the good news is that If you don't fear to play with an unstable environment, you can give a try with the upcoming platform, which already includes a preinstalled JDK "9-ea". You simply have to update your .travis.yml with the following settings:

sudo: required
dist: trusty
group: edge
jdk: oraclejdk9

and you get it 😺

@gsmet if you try this "alpha" environment, please be aware that the maven configuration on this system is broken with JDK9. There might be other integration troubles, and your feedbacks will be very welcome 😄

[gsmet]

@gildegoma

Thanks for your feedback. I spotted a typo here (probably harmless):
https://github.com/travis-ci/travis-cookbooks/pull/587/files#diff-6db6876955404b854c46e46975340a67R60
(java-8 should be java-9)

We indeed do use Maven. Is there a way to fix the Maven configuration by some magic?

My main issue with the Trusty infrastructure is that it looks like the cache is not supported for public repositories (https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments) and caching the .m2/repository really saves a lot of time and resources. Is it something subject to change?

Thanks!

[gildegoma]

@gsmet thanks for the good catch (now fixed)

We'll first validate JDK9-EA in Trusty environment, and I suppose that the Docker-based environment will only be updated when things get really stable. Not having file caching is of course a disadvantage, but it would be great if you try to already integrate on a distinct "testing" branch.

If you want to try JDK9-EA with Maven anyway, you have to take care of the following points:

• set MAVEN_SKIP_RC=true environment variable (because /etc/mavenrc currently contains a -XX:MaxPermSize=192m setting, which is no longer supported by JDK9)
• you'll probably have to tweak your Maven configuration to deal with the absence of lib/tools.jar in the JDK9 installation:
  • http://openjdk.java.net/jeps/220
  • https://issues.apache.org/jira/browse/MNG-5732

[jaredsburrows]

Any update on this?

I get this error:

$ jdk_switcher use oraclejdk9
Sorry, but JDK 'oraclejdk9' is not known.
The command "jdk_switcher use oraclejdk9" failed and exited with 1 during .

When using:

language: java

jdk:
 - oraclejdk8
 - oraclejdk9

matrix:
  allow_failures:
    - jdk: oraclejdk9

[jaredsburrows]

@gsmet Were you able to get jdk9 working?

[vlsi]

I was able to build maven project via jdk9-ea, however the VM takes forever to boot from time to time. For instance: https://travis-ci.org/pgjdbc/pgjdbc/builds/130389303
The vm just gets stuck in "booting" state.
Is it something expected for group: edge?

[vlsi]

Just in case, approach from #4178 (comment) worked for me to install jdk9-ea in Travis docker environment. The drawback is jdk column reads "jdk8", otherwise it works.

Being able to just use oraclejdk9 would be good.

[gildegoma]

http://gradle.org/blog/gradle-3-0-m2-java-9-support/