Skip to content
This repository was archived by the owner on Dec 19, 2023. It is now read-only.

Scope of transitive dependencies #403

Closed
ReneBL opened this issue Apr 25, 2020 · 0 comments
Closed

Scope of transitive dependencies #403

ReneBL opened this issue Apr 25, 2020 · 0 comments
Milestone

Comments

@ReneBL
Copy link

ReneBL commented Apr 25, 2020

When importing some of the starters in a spring-boot application, let's say graphql-kickstart-spring-boot-starter-webflux, some of the autoconfigured beans are marked as @ConditionalOnMissingBean, which is fine if you want to customize something.

The problem is that those bean types classes are placed in runtime-scoped dependencies, so at compile time you won't be able to use them to override or extend some functionalities.

Is that the desired situation? For me it seems cumbersome because you need to copy all dependencies and import them in your project instead of relying on the aforementioned starter

@oliemansm oliemansm added this to the 7.1.0 milestone May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants