[SQL] JavaTypeMapping fails to load when Joda-Time is not in classpath

Bug #856563 reported by Luis Fernando Planella Gonzalez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Querydsl
Fix Released
Undecided
Unassigned

Bug Description

For projects not using Joda-Time, the type registration shouldn't fail.
As a temporary workaround, of course, I can add joda-time-XX.jar to the class path, but my suggestion would be to add a check whether JodaTime classes can be found before attempting to register them in the static initializer on JavaTypeMapping.

Changed in querydsl:
status: New → Fix Committed
Revision history for this message
Timo Westkämper (timo-westkamper) wrote :

Released in 2.2.3

Changed in querydsl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.