-
Notifications
You must be signed in to change notification settings - Fork 38.4k
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
Support for Jackson 2.9 [SPR-14925] #19492
Comments
Juergen Hoeller commented I've upgraded our master build to Jackson 2.9 PR1: no compatibility issues so far. Let's see whether there's anything 2.9-specific that we can support eventually... |
Sébastien Deleuze commented Pull request created to be reviewed by Arjen Poutsma for the Spring MVC side. |
Sébastien Deleuze commented I have added support for returning 5xx status code instead of 4xx for Notice that since I resolve this issue as complete since we are already on 2.9.0.pr2 and I expect no new features to adapt to (expect on Reactive side but their is other issues for that). We will just have to upgrade to 2.9.0 when available. |
Juergen Hoeller commented I've upgraded the build to Jackson 2.9 PR3 now, assuming that's what we're going to release against next week. |
sreekanth commented
|
Juergen Hoeller commented As far as I'm aware, there are no known incompatibilities between Spring Framework 4.3.x and Jackson 2.9.x. We'd certainly be willing to address those if we learn about any such issues. However, first-class Jackson 2.9 support - including special translation of So effectively, Spring Framework 4.3.x - as our long-term support branch - is compatible with Jackson 2.6 up until 2.9, and we'll keep it compatible with Jackson 2.9.x. |
sreekanth commented Sounds great..., thanks |
Juergen Hoeller opened SPR-14925 and commented
Jackson 2.9 is likely to be available in time for our 5.0 GA:
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9
Issue Links:
Referenced from: commits 61a4eaf, 9a501fa, 23e35c0, 4db2daa, 9e8bc95, 113f0fb, ed85658
The text was updated successfully, but these errors were encountered: