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
As the result of the execution of graphql-maven-plugin:graphql two type of source code is generated
17
+
18
+
* The Query, Mutation and POJOs classes
19
+
20
+
* All the necessary runtime classes that do not depend on the schema and support the client execution
21
+
22
+
[]
23
+
24
+
The runtime classes are copied as source code so, your project, when it runs, doesn't depend on any external dependency from graphql-java-generator.
25
+
But if for any reason you don't what the the runtime classes in your generated source code (and you just want to add them as a dependency) it is possible to customize
26
+
the plugin execution so they are not generated
27
+
28
+
29
+
30
+
* {How to use the configure source code generation to no include runtime classes?}
31
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~
32
+
33
+
To avoid the generation of runtime classes you can use the parameter <<copyGraphQLJavaSources>> (-Dcom.graphql_java_generator.mavenplugin.copyGraphQLJavaSources)
34
+
If copyGraphQLJavaSources is "false", then the runtime classes won't be generated. By default, the parameter value is "true"
35
+
36
+
Here there's an exmaple of plugin configuration to not generate runtime classes
Remember that it you decide not to generate runtime classes, <<com.graphql-java-generator:graphql-java-runtime:${lastReleasedVersion}>> shall be somehow included in your classpath
69
+
You may use <<com.graphql-java-generator:graphql-java-runtime:${lastReleasedVersion}>> artifact as a dependency in your project to include graphql-java-runtime in your classpath
0 commit comments