-
Notifications
You must be signed in to change notification settings - Fork 357
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
Jersey 3.0 breaking change #5196
Milestone
Comments
You are right, this paragraph is about migration to 3.0.0, so the statement should be
We'll fix that, thank you for pointing it out. |
Fixed by #5197 |
This was referenced Dec 23, 2022
1 task
1 task
1 task
This was referenced Mar 11, 2023
1 task
This was referenced Mar 23, 2023
Closed
1 task
1 task
1 task
This was referenced Jul 24, 2023
This was referenced Aug 14, 2023
1 task
This was referenced Sep 11, 2023
1 task
1 task
This was referenced Jan 3, 2024
1 task
1 task
Closed
1 task
1 task
This was referenced Jul 9, 2024
1 task
1 task
This was referenced Jan 30, 2025
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the documentation -
https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest3x/migration.html#mig-3.0.0-breaking-changes
the following is stated
The most fundamental change in Jersey 3.1.0 and later is namespace change. Since Jakarta EE 9 the jakarta. namespace is introduced as a replacement for javax namespace from Java EE.
Do you mean this change is from jersey 3.0.0 or 3.1.0 as well as per what can be seen in poms?
The text was updated successfully, but these errors were encountered: