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:
implementation('com.graphql-java-kickstart:graphql-spring-boot-starter:11.0.0') {
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-logging'
exclude group: 'org.springframework.boot', module: 'spring-boot'
exclude group: 'org.springframework.boot', module: 'spring-actuator'
exclude group: 'org.springframework.boot', module: 'spring-actuator-autoconfigure'
exclude group: 'org.springframework.boot', module: 'spring-boot-autoconfigure'
exclude group: 'org.springframework.boot', module: 'spring-boot-starter'
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-actuator'
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-json'
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-tomcat'
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-web'
exclude group: 'org.springframework', module: 'spring-aop'
exclude group: 'org.springframework', module: 'spring-beans'
exclude group: 'org.springframework', module: 'spring-context'
exclude group: 'org.springframework', module: 'spring-core'
exclude group: 'org.springframework', module: 'spring-expression'
exclude group: 'org.springframework', module: 'spring-jcl'
exclude group: 'org.springframework', module: 'spring-web'
}
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?
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?