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

Compile and test on Java 9 #775

Closed
6 tasks done
sormuras opened this issue Apr 6, 2017 · 19 comments
Closed
6 tasks done

Compile and test on Java 9 #775

sormuras opened this issue Apr 6, 2017 · 19 comments

Comments

@sormuras
Copy link
Member

sormuras commented Apr 6, 2017

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

@jbduncan
Copy link
Contributor

jbduncan commented Apr 6, 2017

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?

@sormuras
Copy link
Member Author

sormuras commented Apr 6, 2017

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.

@sbrannen
Copy link
Member

sbrannen commented Apr 6, 2017

@sormuras, thanks for compiling all of this information! 👍

@sbrannen
Copy link
Member

sbrannen commented Apr 6, 2017

FYI: the Shadow plugin has already been upgraded to ASM 5.2: johnrengelman/shadow#285

@sbrannen
Copy link
Member

sbrannen commented Apr 6, 2017

Why not just suppress deprecation warnings on the call for now?

Or... would that mess up the JDK 8 build? 😜

@sbrannen
Copy link
Member

sbrannen commented Apr 6, 2017

It'll also be nice to be able to switch to trySetAccessible(), but we'll have to wait until JUnit 6 for that probably.

@jbduncan
Copy link
Contributor

jbduncan commented Apr 6, 2017

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. :)

@sbrannen
Copy link
Member

sbrannen commented Apr 6, 2017

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.

@jbduncan
Copy link
Contributor

jbduncan commented Apr 6, 2017

Of course.

@reinhapa
Copy link
Contributor

reinhapa commented Apr 6, 2017

I would be happy to help on that as soon you wanted to start on this issue...

@sormuras
Copy link
Member Author

sormuras commented Apr 7, 2017

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.

@sormuras sormuras self-assigned this Apr 7, 2017
@sormuras sormuras changed the title Lessons learned "JUnit 5 - compile and test on Java 9" Compile and test on Java 9 Apr 8, 2017
sormuras added a commit that referenced this issue Apr 8, 2017
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.
@sormuras
Copy link
Member Author

sormuras commented Apr 10, 2017

W/ daemon (default): https://travis-ci.org/junit-team/junit5/builds/220482687 works
W/o daemon (--no-daemon): https://travis-ci.org/junit-team/junit5/builds/220480116 fails

Why?

sormuras added a commit that referenced this issue Apr 10, 2017
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.
sormuras added a commit that referenced this issue Apr 11, 2017
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
sormuras added a commit that referenced this issue Apr 12, 2017
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
sormuras added a commit that referenced this issue Apr 14, 2017
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
sormuras added a commit that referenced this issue Apr 14, 2017
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
sormuras added a commit that referenced this issue Apr 21, 2017
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
@sormuras
Copy link
Member Author

sormuras commented May 4, 2017

All three open ends are still not resolvable:

@joel-costigliola
Copy link

@sormuras AssertJ 3.7.0 should be released in a week or so.

@sormuras
Copy link
Member Author

sormuras commented May 4, 2017

Thanks for the information, Joel! 👍

@marcphilipp marcphilipp modified the milestones: 5.0 M5, 5.0 M6 May 6, 2017
sormuras added a commit that referenced this issue May 7, 2017
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
@sormuras
Copy link
Member Author

sormuras commented May 7, 2017

AssertJ 3.7.0 now used in master via 30581c7

@marcphilipp
Copy link
Member

@johnrengelman Are there any updates regarding Shadow 2.0.0?

@johnrengelman
Copy link

@marcphilipp I'm going to publish it tonight when I get home.

sormuras added a commit that referenced this issue May 10, 2017
@sormuras
Copy link
Member Author

Shadow 2.0.0 now used in master via febcfe9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants