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
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
Receiving this error on running ./gradlew clean build command in plain vanilla java example
Env:
Ubuntu 20.04
opendJDK 11
import org.graphqlize.java.GraphQLResolver;
^
bad class file: /home/user/.gradle/caches/modules-2/files-2.1/org.graphqlize/graphqlize-java/0.1.0-alpha20/5abcf1eb56546b988aeff61fe2ea87d357a7cc36/graphqlize-java-0.1.0-alpha20.jar(/org/graphqlize/java/GraphQLResolver.class)
class file has wrong version 59.0, should be 55.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
/home/user/code/graphqlize-demo/java/vanilla/src/main/java/Program.java:9: error: cannot access GraphQLizeResolver
import org.graphqlize.java.GraphQLizeResolver;
^
bad class file: /home/user/.gradle/caches/modules-2/files-2.1/org.graphqlize/graphqlize-java/0.1.0-alpha20/5abcf1eb56546b988aeff61fe2ea87d357a7cc36/graphqlize-java-0.1.0-alpha20.jar(/org/graphqlize/java/GraphQLizeResolver.class)
class file has wrong version 59.0, should be 55.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
/home/user/code/graphqlize-demo/java/vanilla/src/main/java/Program.java:30: error: cannot find symbol
GraphQLResolver graphQLResolver = new GraphQLizeResolver(dataSource);
^
symbol: class GraphQLResolver
location: class Program
/home/user/code/graphqlize-demo/java/vanilla/src/main/java/Program.java:30: error: cannot find symbol
GraphQLResolver graphQLResolver = new GraphQLizeResolver(dataSource);
^
symbol: class GraphQLizeResolver
location: class Program
4 errors
The text was updated successfully, but these errors were encountered:
Receiving this error on running
./gradlew clean build
command in plain vanilla java exampleEnv:
The text was updated successfully, but these errors were encountered: