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.

Sign up for GitHub

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

Jump to bottom

Change auto-registration in 2.10 to provide "new" (JavaTimeModule) instead of legacy module #126

Closed
cowtowncoder opened this issue Aug 12, 2019 · 0 comments
Closed

Change auto-registration in 2.10 to provide "new" (JavaTimeModule) instead of legacy module #126

cowtowncoder opened this issue Aug 12, 2019 · 0 comments
Milestone
2.10.0.pr2

Comments

@cowtowncoder
Copy link
Member

Up until 2.9, automatic Module registration using ObjectMapper.findAndRegisterModules() (and alternatives) has found the "old" module (JSR310Module) instead of newer JavaTimeModule. This was due to backwards compatibility concerns.
But at this point it seems less likely there are issues regarding setting and since 3.0 will only provide newer module, let's change defaults in 2.10.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.10.0.pr2
Development

No branches or pull requests
1 participant
@cowtowncoder