New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependencies enforced without applying plugin #21911
Comments
That shouldn’t be the case. An opinion will be expressed about the dependency version (via Gradle’s module metadata) but it shouldn’t be enforced. Can you please provide a minimal example that reproduces the problem that you’re seeing? |
sure.
using spring-boot-2.2.8 resolves to h2-1.4.199 as expected. |
Thanks. I see what you mean now. That change in behaviour wasn't intentional. It's happening because the Gradle module metadata for Ideally, the constraints would only be applied that broadly if you used the dependency management plugin or declared a If you want to upgrade the version from the one that Spring Boot specifies in
|
starting with spring-boot-2.3.0 dependencies seem to be enforced even without applying
spring-boot
plugin / dependency management.I couldn't find any changes documented in that respect.
The text was updated successfully, but these errors were encountered: