-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Remove JDK 8 #16418
Remove JDK 8 #16418
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, thanks! I had it on my list but even better if someone else does it :).
I think there are a few more to update such as all the Gradle projects. See here when I had to go the other way: https://github.com/quarkusio/quarkus/pull/16137/files (and all the other projects were targeting Java 8).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+💯 for kicking it out!
There are a few profile activations related to JDK 8, e.g. this in build-parent
:
<profile>
<id>jdk-8-classpath</id>
<activation>
<!-- activate this on any JDK from 9 onwards -->
<jdk>[9,)</jdk>
</activation>
<properties>
<maven.compiler.release>8</maven.compiler.release>
</properties>
</profile>
I think <jdk>
is a good search term to find all.
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building b80b66b
Test Failures⚙️ JVM Tests - JDK 15 #📦 integration-tests/kafka✖
|
There is a bug in the UPDATE: This is fixed in |
It just occured to me that once we merge this, backports might get more complicated as people will start using Java 11 APIs. |
This is planned for the 2.x releases. How would that be more complicated? |
I meant as long as 1.x branches shall receive backports from |
402d1f4
to
ab65ac4
Compare
41fdce4
to
48995e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the JDK 8 profiles in those three pom.xml should be removed as well:
extensions/grpc/deployment/pom.xml
integration-tests/grpc-mutual-auth/pom.xml
integration-tests/grpc-tls/pom.xml
It might then also be possible to remove boring-ssl
from build-parent
.
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 48995e9
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 11 #📦 integration-tests/kafka✖ ✖ ⚙️ JVM Tests - JDK 15 #📦 integration-tests/kafka✖ ✖ ⚙️ Maven Tests - JDK 11 #📦 integration-tests/maven✖ |
JDK 11 is now the minimum to build Quarkus Remove jdk-8-classpath profile Remove jdk-8-classpath profile from independent projects Update build.gradle Fixed gradle tests
Failing Jobs - Building 21dc993
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 15 #📦 integration-tests/kafka✖ ✖ ⚙️ Maven Tests - JDK 11 #📦 integration-tests/maven✖ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now!
I've seen all those build failures before in other PRs so I don't think they are related.
I thought about adding a thumbs up to the PR but you have 11, which is perfect :). Thanks for this, let's merge and iterate from there if we find other things to adapt. |
JDK 11 is now the minimum to build Quarkus