JSON argument source fails with LocalDate property deserialization

For some odd reason I get an exception while deserializing java.time.LocalDate properties:

Failed to convert to type class com.foo.bar.MyClass
java.io.UncheckedIOException: Failed to convert to type class com.foo.bar.MyClass
	at org.junitpioneer.jupiter.json.JacksonNode.toType(JacksonNode.java:51)
	at org.junitpioneer.jupiter.json.JacksonNode.value(JacksonNode.java:85)
...	
Caused by: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Java 8 date/time type `java.time.LocalDate` not supported by default: add Module "com.fasterxml.jackson.datatype:jackson-datatype-jsr310" to enable handling
 at [Source: UNKNOWN; byte offset: #UNKNOWN] (through reference chain: com.foo.bar.MyClass["someDate"])

The JSR-310 Jackson datatype dependency is in the classpath, but upon further inspection the ObjectMapper instance in org.junitpioneer.jupiter.json.JacksonJsonConverter has no registered modules.

Any way to fix this? Or better yet provide a way to customize the used ObjectMapper instance? Right now I’m working around this by using reflection to manually register the module.

Using Gradle 7.1.1 on OpenJDK 11 with classpath.

[beatngu13]

Hi @virtual-machinist,

thx for reaching out – we will look into this.

[robtimus]

For #629 I have some uncommitted changes that register a Jdk8Module and a JavaTimeModule if these are available, and a KotlinModule if it’s available and so is Kotlin (check on class kotlin.Metadata). I can create a new PR for that.

Maven users indeed would need to add jackson-datatype-jdk8 and jackson-datatype-jsr310 to their dependencies, but odds are that they already have these as compile or runtime dependencies if they need them in their JSON test definitions, because they most likely need them in their main code as well.