Improve reference docs on how to find schema files acorss multiple modules

[toinetoine]

I couldn't find anywhere in the documentation (or examples) how to include schema file from imported maven modules.

Background: We have an external project with the entities (models) and pull it in as a maven dependency. The graphqls schema files with the type declarations for each entity lives in that project.

Using legacy GraphQL Java Kickstart it automatically picked up graphqls schema files from maven dependencies (imported jars). Is there a way to do this using new spring-boot-starter-graphql?

I uploaded a demo project showing what we are trying to do. Right now the schema file in the app module is being picked up (highlighted in green) but the schema in the app module's dependency animals module is not being picked up (highlighted in red).

When I move the the schema file in the animals module to the app module (renaming it to schema2.graphql) it works.

I tried using spring.graphql.schema.locations=classpath:/graphql/,BOOT-INF/lib/animals-0.0.1-SNAPSHOT.jar!/graphql/ using the path to the schema files from the jar but it didn't work.

Also tried using the default (not specifying in my application properties at all) but didn't work.

[bclozel]

Does the following work for your application?

spring.graphql.schema.locations=classpath*:graphql/**/

[toinetoine]

Thank you! Adding spring.graphql.schema.locations=classpath*:graphql/**/ to application properties caused all schema from other modules to be picked up.

[rstoyanchev]

I think we can improve the Javadoc a bit.

[bclozel]

Thanks for reopening this issue @rstoyanchev - this has appeared again in the Spring Boot issue tracker as well, see spring-projects/spring-boot#31772. I'm thinking this happens often enough that we should reconsider the default property value in Spring Boot 3.0 to switch to using classpath*:. What do you think?