-
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
Joda-Time presence check fails to detect Joda-Time 2.x specifically #25655
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
Comments
Thanks for the report. I think this should be addressed in Spring Framework. |
jhoeller
added a commit
that referenced
this issue
Aug 28, 2020
jhoeller
added a commit
that referenced
this issue
Aug 28, 2020
engimatic
pushed a commit
to engimatic/spring-framework
that referenced
this issue
Sep 29, 2020
zx20110729
pushed a commit
to zx20110729/spring-framework
that referenced
this issue
Feb 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
We upgrade our project from 2.2.1 to 2.3.3 and now we are getting this exception. We found that you are no longer managing joda-time (in past it was 2.10.5) but query-dsl( managed 4.3.1) brings 1.6.
The
DefaultFormattingConversionService
detectes joda time on the classpath and calls theJodaTimeFormatterRegistrar#registerFormatters
which contains the following lines. Which both references not existing classes in joda 1.6 (YearMonth
andMonthDay
) both were added in joda 2.0 according to the javadoc.The text was updated successfully, but these errors were encountered: