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

Jakarta EE 9 and Microprofile 5 spec/API alignment #22521

Closed
hantsy opened this issue Dec 25, 2021 · 3 comments
Closed

Jakarta EE 9 and Microprofile 5 spec/API alignment #22521

hantsy opened this issue Dec 25, 2021 · 3 comments
Labels
triage/duplicate This issue or pull request already exists

Comments

@hantsy
Copy link
Contributor

hantsy commented Dec 25, 2021

Description

Migrate to the latest Jakarta EE 9 and Microprofile v5 and Java 17 based.

Analysis

Spring 6 will align with Jakarta EE 9 and introduce built-in native features, and Micornaut 3 already support both Jakarta EE 8 and Jakarta EE 9 API(I have tried jakarta.inject, jakarta.annoations, etc).

Quarkus has any plan of upgrading to the latest Jakarta EE 9 and Microprofile v5?

@hantsy hantsy added the kind/epic Large issue with links to sub-issues label Dec 25, 2021
@geoand
Copy link
Contributor

geoand commented Jan 3, 2022

cc @radcortez

@radcortez
Copy link
Member

Quarkus has any plan of upgrading to the latest Jakarta EE 9 and Microprofile v5?

MP 5.0 only provided Jakarta compatible binaries in December. We now need to move all of the SmallRye implementations to use Jakarta (and this is only covering the MP side).

Unfortunately, this is not an easy thing to do, especially since it requires that dependencies are ready to support Jakarta.

@gastaldi
Copy link
Contributor

gastaldi commented Jan 4, 2022

Duplicate of #21574

@gastaldi gastaldi marked this as a duplicate of #21574 Jan 4, 2022
@gastaldi gastaldi closed this as completed Jan 4, 2022
@gastaldi gastaldi added triage/duplicate This issue or pull request already exists and removed kind/epic Large issue with links to sub-issues labels Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants