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.

Sign up for GitHub

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

fix typo #1847

Merged
merged 1 commit into from
Nov 30, 2023
Merged

fix typo #1847

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2023-11-30-java-17.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ ifdef::env-github,env-browser,env-vscode[:imagesdir: ../assets/images/posts/]

Today we are anouncing that Quarkus 3.7 will move Quarkus to use Java 17 as the minimum JDK.

When we started Quarkus 3.0, https://quarkus.io/blog/road-to-quarkus-3/#java-target[we stayed on Java 11]. The feedback we got was that moving to Jakarta EE 10 was for many easier than to also move the underlyng JDK. We wanted to give the ecosystem time to catch up and make sure we had a good story for users that needed to stay on Java 11.
When we started Quarkus 3.0, https://quarkus.io/blog/road-to-quarkus-3/#java-target[we stayed on Java 11]. The feedback we got was that moving to Jakarta EE 10 was for many easier than to also move the underlying JDK. We wanted to give the ecosystem time to catch up and make sure we had a good story for users that needed to stay on Java 11.

In 3.0 release, we supported Java 11 for Quarkus core, and we https://quarkus.io/blog/quarkus-3-0-final-released/#java-11-deprecated[marked Java 11 as deprecated]. It should be noted that parts of the platform, especially the Camel Extensions for Quarkus, already require Java 17.

Expand Down
Loading