Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get jdk-9 back to build JUnit 5 #842

Merged
merged 4 commits into from
May 15, 2017
Merged

Conversation

sormuras
Copy link
Member

@sormuras sormuras commented May 7, 2017

Overview

Current state of getting jdk-9 back to build JUnit 5 - not only on Travis CI.

With 4e401dd the '-Werror' compiler option is untouched, i.e. remains activated.

Fixes #775

Note

Travis CI (debian trusty) is still on JDK9-B162, due to webupd8team is on 162.

Using a manually installed JDK9-B168 with d0443a3 for now.


I hereby agree to the terms of the JUnit Contributor License Agreement.


Definition of Done

sormuras added 3 commits May 7, 2017 20:25
Direct Travis build script to install JDK-9 (9b162 as of this commit)
and set `JDK_JAVA_OPTIONS` that allow Gradle to run on Java 9.
There is a regression in JDK-9 b162 that leads to an exception: "Cannot
create Launcher for multiple engines with the same ID 'xyz'".

See https://bugs.openjdk.java.net/browse/JDK-8177139 for details

This commit can be reverted when Travis CI installs a JDK-9 b163 or higher.
This reverts the test engine pruning needed by the old jdk-9 b162
@sormuras sormuras force-pushed the issues/775-compile-and-test-on-jdk9 branch from 7ac845f to d0443a3 Compare May 15, 2017 12:25
@sormuras sormuras merged commit fc86038 into master May 15, 2017
@sormuras sormuras deleted the issues/775-compile-and-test-on-jdk9 branch May 15, 2017 18:12
@sormuras sormuras modified the milestones: 5.0 M5, 5.0 M6 May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants