You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A runtime error (java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/util/JacksonFeature) occurs after adding com.graphql-java-kickstart:graphql-java-servlet as dependency. This is not the case for earlier versions of com.graphql-java-kickstart:graphql-java-servlet.
examples.zip contains minimal examples that produce this behaviour:
graphql-ok:
only dependency is com.graphql-java-kickstart:graphql-java-tools:11.0.1 (latest release).
io.dama.graphql.Main works.
graphql-still-ok:
additional dependency com.graphql-java-kickstart:graphql-java-servlet:10.1.0 together with com.graphql-java-kickstart:graphql-java-tools:6.3.0
lets io.dama.graphql.Main still in a working condition .
graphql-not-ok:
latest releases of the two dependencies (com.graphql-java-kickstart:graphql-java-servlet:11.1.1 and com.graphql-java-kickstart:graphql-java-tools:11.0.1)
makes io.dama.graphql.Main crash at runtime.
This behaviour is not specific to Java 16.
Expected behavior
No runtime error while running io.dama.graphql.Main with latest releases of the two dependencies (com.graphql-java-kickstart:graphql-java-servlet:11.1.1 and com.graphql-java-kickstart:graphql-java-tools:11.0.1) .
Actual behavior
see graphql-not-ok: io.dama.graphql.Main produces a java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/util/JacksonFeature
Steps to reproduce the bug
Build the 3 Maven projects in examples.zip and try to run io.dama.graphql.Main in each of these.
The text was updated successfully, but these errors were encountered:
examples.zip
Description
A runtime error (
java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/util/JacksonFeature
) occurs after addingcom.graphql-java-kickstart:graphql-java-servlet
as dependency. This is not the case for earlier versions ofcom.graphql-java-kickstart:graphql-java-servlet
.examples.zip
contains minimal examples that produce this behaviour:graphql-ok
:com.graphql-java-kickstart:graphql-java-tools:11.0.1
(latest release).io.dama.graphql.Main
works.graphql-still-ok
:com.graphql-java-kickstart:graphql-java-servlet:10.1.0
together withcom.graphql-java-kickstart:graphql-java-tools:6.3.0
io.dama.graphql.Main
still in a working condition .graphql-not-ok
:com.graphql-java-kickstart:graphql-java-servlet:11.1.1
andcom.graphql-java-kickstart:graphql-java-tools:11.0.1
)io.dama.graphql.Main
crash at runtime.This behaviour is not specific to Java 16.
Expected behavior
No runtime error while running
io.dama.graphql.Main
with latest releases of the two dependencies (com.graphql-java-kickstart:graphql-java-servlet:11.1.1
andcom.graphql-java-kickstart:graphql-java-tools:11.0.1
) .Actual behavior
see
graphql-not-ok
:io.dama.graphql.Main
produces ajava.lang.NoClassDefFoundError: com/fasterxml/jackson/core/util/JacksonFeature
Steps to reproduce the bug
Build the 3 Maven projects in
examples.zip
and try to runio.dama.graphql.Main
in each of these.The text was updated successfully, but these errors were encountered: