-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Compile and test on Java 9 #775
Comments
I'm curious as to why build warnings should not be treated as errors. How long should they not be treated as errors, if it's just a temporary measure? |
It's just a temporary measure to not break the build at https://travis-ci.org/junit-team/junit5/builds/219251561#L752 ... which should use AccessibleObject.canAccess as soon as we switch to Java 9. |
@sormuras, thanks for compiling all of this information! 👍 |
FYI: the Shadow plugin has already been upgraded to ASM 5.2: GradleUp/shadow#285 |
Why not just suppress deprecation warnings on the call for now? Or... would that mess up the JDK 8 build? 😜 |
It'll also be nice to be able to switch to trySetAccessible(), but we'll have to wait until JUnit 6 for that probably. |
Alternatively to waiting for JUnit 6, we might be able to use MR-JAR support coming with Java 9, once we have a clear picture of how MR-JARs fit into Gradle. :) |
Ummmm... yeah... once we can actually (reliably) develop against Java 9 with the whole tool chain (Gradle, all CI servers, IDEs, etc.). So, I'm not going to hold my breath for that at the moment. |
Of course. |
I would be happy to help on that as soon you wanted to start on this issue... |
http://mailman.qos.ch/pipermail/announce/2017/000146.html Ceki just released SLF4J version 1.8.0-alpha0, modularized for Java9/Jigsaw/JPMS/JSR 376, on Maven Central. Let's have look how he did. |
This commit removes failing jdk-9 build and caching. * Java 9 will be re-installed by #775. * Caching gradle and dependency binaries did not result in build speed-ups and the applied "--refresh-dependencies" did by-pass the cache anyway.
W/ daemon (default): https://travis-ci.org/junit-team/junit5/builds/220482687 works Why? |
This commit removes failing jdk-9 build and caching. * Java 9 will be re-installed by #775. * Caching gradle and dependency binaries did not result in build speed-ups and the applied "--refresh-dependencies" did by-pass the cache anyway.
Upgrade to AssertJ 3.7.0-SNAPSHOT (using jitpack) Use JDK_JAVA_OPTIONS to open java.base and other packages ServiceLoader.load() loads providers multiple times - prune 'em Addresses: #775
Upgrade to AssertJ 3.7.0-SNAPSHOT (using jitpack) Use JDK_JAVA_OPTIONS to open java.base and other packages ServiceLoader.load() loads providers multiple times - prune 'em Addresses: #775
Upgrade to AssertJ 3.7.0-SNAPSHOT (using jitpack) Use JDK_JAVA_OPTIONS to open java.base and other packages ServiceLoader.load() loads providers multiple times - prune 'em Addresses: #775
Upgrade to AssertJ 3.7.0-SNAPSHOT (using jitpack) Use JDK_JAVA_OPTIONS to open java.base and other packages ServiceLoader.load() loads providers multiple times - prune 'em Addresses: #775
Upgrade to AssertJ 3.7.0-SNAPSHOT (using jitpack) Use JDK_JAVA_OPTIONS to open java.base and other packages ServiceLoader.load() loads providers multiple times - prune 'em Addresses: #775
All three open ends are still not resolvable:
|
@sormuras AssertJ 3.7.0 should be released in a week or so. |
Thanks for the information, Joel! 👍 |
Upgrade to AssertJ 3.7.0 Use JDK_JAVA_OPTIONS to open java.base and other packages ServiceLoader.load() loads providers multiple times - prune 'em Addresses: #775
AssertJ 3.7.0 now used in master via 30581c7 |
@johnrengelman Are there any updates regarding Shadow 2.0.0? |
@marcphilipp I'm going to publish it tonight when I get home. |
Shadow 2.0.0 now used in master via febcfe9 |
Moved "Lessons learned..." to Wiki
Lessons learned "JUnit 5 compile and test on Java 9 b162"
Here, only the remaining technical steps resulting from the lessons learned are retained.
Related Issues
Deliverables
.travis.yml
script -- via a313a07Report andremove workaround for ServiceLoader "bug" when "everybody" has access to build 163The text was updated successfully, but these errors were encountered: