Jakarta 11, Spring Boot 4#2
Draft
jacekbilski wants to merge 6 commits into
Draft
Conversation
Signed-off-by: Jacek Bilski <jacek@bilski.tech>
Signed-off-by: Jacek Bilski <jacek@bilski.tech>
Signed-off-by: Jacek Bilski <jacek@bilski.tech>
Signed-off-by: Jacek Bilski <jacek@bilski.tech>
Signed-off-by: Jacek Bilski <jacek@bilski.tech>
Signed-off-by: Jacek Bilski <jacek@bilski.tech>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the fourth PR of the series towards Java 17 / Spring Boot 4 / Quarkus 3 / Jakarta EE 11.
We're finally on Jakarta 11 and are using Spring Boot 4 and Jackson 3. I migrated most samples and tests to use Jackson 3, but left some just to show, that Jackson 2 is still here. Feel free to disagree, I could migrate everything else.
Two notes/questions though:
io.cloudevents.formats.jackson3. That way we're not forcing anyone to migrate to Jackson 3, for a time being they can use Jackson 2. But the naming means we'll have this "3" dangling at the end for quite some time, until Jackson 4 comes out or is completely replaced by something else. The other option could be to rename currentjacksonmodule tojackson2and name the new onejackson. But that would be a breaking change, people will get confused. One other, even more drastic, option would be to completely drop Jackson 2 and leave Jackson 3. But Jackson 2 still lives, has its LTS versions released. I guess, that would be too far-going. What's your opinion on this?