External schema library and code, how do I include in my schema?

[n614cd]

Problem: To have a project include the schema files and the associated class files from a library project. Is this possible?

Background:

• I have a Java code library I built, which includes schema files and the associated classes built via dgsCodegen; this is pushed to a private maven repository; the library uses Gradle as the build tool.
• The main project has multiple sub-projects. The idea is for a subproject to contain a schema and related class files generated via dgsCodegen and which also includes the complete schema and classes from the library.
• I have included the reference to the library via

dependencies {

	dgsCodegen 'XXXX:YYYY:ZZZZ'
}

• Using "gradlew subproject:dependencies > x.x" I can verify dgsCodegen has the proper dependency of my additional library.

dgsCodegen
\--- XXXX:YYYY:ZZZZZ
     +--- com.netflix.graphql.dgs.codegen:graphql-dgs-codegen-gradle:6.1.0
     |    +--- org.jetbrains.kotlin:kotlin-bom:1.9.20

• In Eclipse, I have opened the jar file, and I can see both the generated classes and the schema files.
• Symptoms that I missed something. Running gradlew subproject:clean subproject:generateJava --info I do not see the expected scanning of the dependent library.
• The subproject schema includes references to types defined in the library project, and they are not generated which is then giving compile errors.
• The package names will differ between the library and the main projects.
• graphql-dgs-platform-dependencies is version 8.2.0'
• graphql-dgs-codegen-gradle is version = '6.1.0'

[n614cd]

using --debug I did track down part of the issue. Gradle was not correctly handling a cache issue and was not actually having dgsCodegen update before execution. After wiping all local gradle files/caches, and doing a fresh clone of the repository dgsCodegen does generate the per the directions: https://netflix.github.io/dgs/generating-code-from-schema/#generating-code-from-external-schemas-in-jars

However, I effectively still have the problem with package conflicts, since the generated model in the parent project uses a different package names.

I have yet to solve the issue of multiple libraries with dgsCodegen and dgsFramework in a single parent project.

Tim

[n614cd]

My final solution works. Kind of a hack, but it does work.
II create a property file with the full package plus class name of the class to be replaced with the value it should be replaced with. This allows me to on a class by class basis correct the packages.

In my build.gradle script I then have the following.

generateJava {
schemaPaths = ["${projectDir}/src/main/resources/com/XXXXX/YYYY/schema"]
packageName = 'com.XXXXX.YYYYY.model'
generateClient = true
}

task fixClassPackage {
doLast {
ant.replace(replacefilterfile:'model-class-swap.properties', dir: 'build/generated/sources/dgs-codegen', includes: '**/*.java');
}
}

tasks.named('fixClassPackage') { dependsOn('generateJava') }
tasks.named('eclipse') { dependsOn('fixClassPackage') }
tasks.named('build') { dependsOn('fixClassPackage') }