Possibility to add graphql to existing springbootproject #607
Replies: 2 comments 2 replies
-
@wiedehoeft I've converted your issue to a Q&A Discussion seeing you're actually asking a question and not (yet) reporting a bug or asking for a feature. The graphql-spring-boot-starter currently indeed pulls in the Spring Boot starters too. So the solutions you're mentioning are indeed the ones that you're stuck with at this time unfortunately. Do you really need to specify all modules too, because I thought those were optional and you could make the above a lot shorter. The next major release will contain several breaking changes. One of which will be that it'll no longer pull in any spring-boot-starters, but instead expects them to be provided by the user. We will however try to stay up to date with Spring Boot versions, which means that it could be that it some point our libraries are no longer compatible with older Spring Boot versions. |
Beta Was this translation helpful? Give feedback.
-
We have just detected that there is an other endpoint present: /graphql/subscribe. |
Beta Was this translation helpful? Give feedback.
-
Hi,
which dependencies would you add to an existing springboot project?
The graphql dependency seems to add all dependencies, which an existing springboot project already have, again.
After adding graphql-spring-boot we have had many dependencies on classpath twice, which results in classpath resolution problems.
The current workaround is a list like this:
But with this configuration we have trouble with our Wildfly deployment.
The only other solution seems to be, to lookup the spring boot version from graphql-spring-boot and use the same version in existing spring-boot project, or did we miss something?
Beta Was this translation helpful? Give feedback.
All reactions