Release com.kobylynskyi.graphql.codegen.model.graphql as a separate artifact

Is your feature request related to a problem? Please describe. Our project consists of three sub-projects:

• foo-api
• foo-client
• foo-service

The generator is run in the foo-service project, which builds the models for the foo-api project. foo-client performs the serialization and makes the http requests for service-to-service communication. To keep the projects lightweight, we only want to include the necessary client dependencies in the api and client projects rather than the full code-generator dependency.

Describe the solution you’d like The package com.kobylynskyi.graphql.codegen.model.graphql to be split out into its own project and released separately alongside future builds of the project. I don’t really have a recommendation or expectation for naming of this new project.

Describe alternatives you’ve considered We implemented the proposed fix locally in our project and included our temporary solution as an api dependency in the foo-api and foo-client projects and everything works as we would expect.

[dspenceb]

I agree that this solution is a bit better than what we currently have, but I feel having any dependency is somewhat of a smell. Could these classes appear as part of the “generated” pool of classes? This could eliminate the need to depend on anything outside and I think would be the lightest weight solution by far.

[kobylynskyi]

5.0.0 was released. graphql-java and other libraries are now excluded from the classpath of graphql-java-codegen so please try upgrading graphql-java-codegen to 5.0.0. Thanks.