graphqlcodegen-maven-plugin-3.7.0

What's Changed

• Dgs codegen dependency update by @deweyjose in #296

Full Changelog: graphqlcodegen-maven-plugin-3.6.1...graphqlcodegen-maven-plugin-3.7.0

graphqlcodegen-maven-plugin-3.6.1

What's Changed

• Bump ch.qos.logback:logback-classic from 1.5.18 to 1.5.20 by @dependabot[bot] in #287
• Bump com.graphql-java:graphql-java from 24.1 to 24.3 by @dependabot[bot] in #288
• Bump org.projectlombok:lombok from 1.18.38 to 1.18.42 by @dependabot[bot] in #289
• Bump org.jacoco:jacoco-maven-plugin from 0.8.13 to 0.8.14 by @dependabot[bot] in #290
• Bump org.mockito:mockito-core from 5.18.0 to 5.20.0 by @dependabot[bot] in #291
• Dgs codegen dependency update by @deweyjose in #295

Full Changelog: graphqlcodegen-maven-plugin-3.6.0...graphqlcodegen-maven-plugin-3.6.1

graphqlcodegen-maven-plugin-3.6.0

What's Changed

• fix build by @deweyjose in #286
• Bump org.codehaus.mojo:flatten-maven-plugin from 1.7.0 to 1.7.3 by @dependabot[bot] in #281
• Bump org.jetbrains.kotlin:kotlin-stdlib from 2.1.21 to 2.2.21 by @dependabot[bot] in #283
• Bump org.jetbrains.kotlin:kotlin-compiler-embeddable from 2.1.21 to 2.2.21 by @dependabot[bot] in #284
• Bump org.jetbrains.kotlin:kotlin-reflect from 2.1.21 to 2.2.21 by @dependabot[bot] in #285
• Bump com.diffplug.spotless:spotless-maven-plugin from 2.44.4 to 3.0.0 by @dependabot[bot] in #282
• Graphql codegen library update by @deweyjose in #294

Please note

omitNullInputFields is no longer a configurable option in the underlying dgs-codegen library. Please remove from your configurations.

Full Changelog: graphqlcodegen-maven-plugin-3.5.1...graphqlcodegen-maven-plugin-3.6.0

graphqlcodegen-maven-plugin-3.5.1

What's Changed

• Bump junit.version from 5.12.2 to 5.13.1 by @dependabot[bot] in #255
• Bump org.apache.maven:maven-core from 3.9.9 to 3.9.10 by @dependabot[bot] in #258
• Bump org.jetbrains.kotlin:kotlin-stdlib from 1.9.23 to 2.1.21 by @dependabot[bot] in #257
• Bump com.fasterxml.jackson.core:jackson-databind from 2.15.2 to 2.19.1 by @dependabot[bot] in #256
• Bump com.fasterxml.jackson.core:jackson-annotations from 2.15.2 to 2.19.1 by @dependabot[bot] in #254
• Fix #270: Update README.md to use correct property name generateClientApiv2 by @deweyjose in #271
• Add lifecycle-mapping-metadata.xml for m2e (Eclipse, VSCode) by @brychcy in #267

New Contributors 🚀 🎸

• @brychcy made their first contribution in #267

Full Changelog: graphqlcodegen-maven-plugin-3.5.0...graphqlcodegen-maven-plugin-3.5.1

graphqlcodegen-maven-plugin-3.5.0

What's Changed

• Bump org.jetbrains.kotlin:kotlin-reflect from 1.9.23 to 2.1.21 by @dependabot in #229
• Bump org.mockito:mockito-core from 5.2.0 to 5.18.0 by @dependabot in #249
• Bump org.apache.maven:maven-plugin-api from 3.9.9 to 3.9.10 by @dependabot in #250
• Bump com.graphql-java:graphql-java from 24.0 to 24.1 by @dependabot in #251

Full Changelog: graphqlcodegen-maven-plugin-3.4.0...graphqlcodegen-maven-plugin-3.5.0

Version 3.5.0 introduces schema transformation for DGS Client compatibility

This release adds automatic transformation of custom root type names to standard GraphQL types, solving compatibility issues when working with remote GraphQL servers that use non-standard root type names.

The Problem

Many GraphQL servers use custom root type names like CustomQuery, CustomMutation, or CustomSubscription instead of the standard Query, Mutation, and Subscription. While this works fine for server-side operations, DGS Client codegen expects standard root type names and fails to generate client code for these schemas.

The Solution

The plugin now automatically transforms custom root types to their standard equivalents during code generation:

# Remote server schema (custom root types)
schema {
    query: CustomQuery
    mutation: CustomMutation
    subscription: CustomSubscription
}

type CustomQuery {
    hello: String
}

# Generated client code (standard root types)
type Query {
    hello: String
}

Key Benefits

• Seamless DGS Client integration - Generate working client code from any GraphQL schema
• No server changes required - Works with existing remote servers that use custom root types
• Transparent transformation - The GraphQL operations sent over the wire maintain the expected shape for the server
• Backward compatible - Existing schemas with standard root types continue to work unchanged

When to Use

This feature is primarily useful for client-side code generation when connecting to remote GraphQL servers that use custom root type names. The transformation ensures DGS Client can generate compatible code while preserving the original schema structure for server communication.

graphqlcodegen-maven-plugin-3.4.0

What's Changed

• feat: add support for local type mapping properties files by @deweyjose in #252

Full Changelog: graphqlcodegen-maven-plugin-3.3.2...graphqlcodegen-maven-plugin-3.4.0

graphqlcodegen-maven-plugin-3.3.2

What's Changed

• Bump org.jacoco:jacoco-maven-plugin from 0.8.12 to 0.8.13 by @dependabot in #230
• remove build-helper by @deweyjose in #243
• Bump org.jetbrains.kotlin:kotlin-compiler-embeddable from 1.9.23 to 2.1.21 by @dependabot in #232
• Bump org.codehaus.mojo:flatten-maven-plugin from 1.5.0 to 1.7.0 by @dependabot in #233
• migrate to java collections by @deweyjose in #244
• update DGS to 8.1.0 by @deweyjose in #247

Full Changelog: graphqlcodegen-maven-plugin-3.3.1...graphqlcodegen-maven-plugin-3.3.2

Please Note

The DGS team removed support for maxProjectionDepth in 8.1.0, as such the options was removed from this plugin.

graphqlcodegen-maven-plugin-3.3.1

What's Changed

• Replace maven-project with maven-core 3.9.9 and update plugin version by @deweyjose in #242

Full Changelog: graphqlcodegen-maven-plugin-3.3.0...graphqlcodegen-maven-plugin-3.3.1

Thanks @wleese for the heads up!

graphqlcodegen-maven-plugin-3.3.0

🚀 New Feature: Remote Schema Introspection-Based Codegen! 🎉

Backend GraphQL developers, your wait is over!
You can now generate Java/Kotlin code directly from remote GraphQL schemas using introspection—right from your Maven build.

No more manual schema downloads or copy-pasting SDL files. Just point the plugin at your GraphQL endpoint, and let it fetch, introspect, and generate types for you—complete with support for custom queries, operation names, and HTTP headers.

Why is this awesome?

• Instantly sync your code with the latest schema from any GraphQL server.
• Automate codegen for internal, partner, or public APIs.
• Easily handle authentication and custom headers.

How to use:
Check out the new introspectionRequests parameter in the plugin configuration documentation

⚠️ Heads up: This feature is brand new and still experimental. We’d love your feedback—try it out, break it, and let us know what you think!

Happy coding! 🚀

What's Changed

• feature/introspection to sdl by @deweyjose in #238
• Feature/sdl from introspection by @deweyjose in #239
• Feature/introspection schemafile service by @deweyjose in #240
• Introspection test by @deweyjose in #241

Full Changelog: graphqlcodegen-maven-plugin-3.2.0...graphqlcodegen-maven-plugin-3.3.0

graphqlcodegen-maven-plugin-3.2.0

What’s Changed

• Added support for using the plugin without requiring the generated source directory to be manually added to compile paths — #236 by @wleese
• Documented the addSources parameter, shift execution post success — #237 by @deweyjose

Thanks to @wleese for the great idea and contribution!

As a result of this change, you no longer need to include the build-helper-maven-plugin in your build configuration just to add the GraphQL Codegen plugin’s generated sources. This is now handled automatically.

If you still prefer to manage source compile classpaths manually, you can disable this feature by setting:

<autoAddSource>false</autoAddSource>

Full Changelog: graphqlcodegen-maven-plugin-3.1.0...graphqlcodegen-maven-plugin-3.2.0