-
Notifications
You must be signed in to change notification settings - Fork 355
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
SpringComponentProvider in jersey-spring6 never binds components #5093
Milestone
Comments
thank you for reporting that. You are right. This shall be added to the multi-release jar. It requires modification of the release script. |
Release script is modified (for Jakarta Jersey 9 and 10) and will be available since the next release (3.0.6 and 3.1.0 respectively) |
This was referenced Aug 5, 2022
Merged
1 task
1 task
This was referenced Sep 23, 2022
1 task
1 task
This was referenced Mar 23, 2023
Closed
1 task
1 task
1 task
1 task
1 task
1 task
1 task
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
Open
1 task
1 task
This was referenced Jul 9, 2024
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would appear that the
jersey-spring6
artifact on Maven Central contains the result of compiling https://github.com/eclipse-ee4j/jersey/blob/3.x/ext/spring6/src/main/javaPre17/org/glassfish/jersey/server/spring/SpringComponentProvider.java rather than https://github.com/eclipse-ee4j/jersey/blob/3.x/ext/spring6/src/main/java17/org/glassfish/jersey/server/spring/SpringComponentProvider.java. I believe it needs to contain the result of compiling the latter to work correctly.Looking at the bytecode using
javap
confirms that bind is hardcoded to returnfalse
:The text was updated successfully, but these errors were encountered: