Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@mspiess
Copy link
Contributor

@mspiess mspiess commented Jan 14, 2026

Spring Projects that have the spring.graphql.schema.locations property set to "classpath*:graphql/**/" as suggested in the documentation have failing GraphQL tests after upgrading to Spring Boot 4. The Query type definition in the books-domain schema clashes with the schema of the application. Presumably the books-domain schema was never meant to exist in the exported JAR file. This commit moves it into the test module to stop it from being exported and causing problems.

Spring Projects that have the `spring.graphql.schema.locations` property
set to `"classpath*:graphql/**/"` as suggested in the documentation have
failing GraphQL tests after upgrading to Spring Boot 4.
The `Query` type definition in the books-domain schema clashes with the
schema of the application. Presumably the books-domain schema was never
meant to exist in the exported JAR file. This commit moves it into the
test module to stop it from being exported and causing problems.

Signed-off-by: mspiess <[email protected]>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 14, 2026
@philwebb philwebb added type: regression A regression from a previous release and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 15, 2026
@philwebb philwebb added this to the 4.0.x milestone Jan 15, 2026
@philwebb philwebb changed the title Move schema.graphqls into test module Setting graphql schema location to "classpath*:graphql/**/" causes failure due incorrectly package test resource Jan 15, 2026
@philwebb philwebb changed the title Setting graphql schema location to "classpath*:graphql/**/" causes failure due incorrectly package test resource Setting graphql schema location to "classpath*:graphql/**/" causes failure due incorrectly packaged test resource Jan 15, 2026
@wilkinsona wilkinsona changed the title Setting graphql schema location to "classpath*:graphql/**/" causes failure due incorrectly packaged test resource Setting graphql schema location to "classpath*:graphql/**/" causes failure due to incorrectly packaged test resource Jan 15, 2026
@wilkinsona wilkinsona modified the milestones: 4.0.x, 4.0.2 Jan 15, 2026
wilkinsona pushed a commit that referenced this pull request Jan 15, 2026
Spring Projects that have the `spring.graphql.schema.locations` property
set to `"classpath*:graphql/**/"` as suggested in the documentation have
failing GraphQL tests after upgrading to Spring Boot 4.
The `Query` type definition in the books-domain schema clashes with the
schema of the application. Presumably the books-domain schema was never
meant to exist in the exported JAR file. This commit moves it into the
test module to stop it from being exported and causing problems.

Signed-off-by: mspiess <[email protected]>

See gh-48829
@wilkinsona
Copy link
Member

Thanks very much, @mspiess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: regression A regression from a previous release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants