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
Scope of some dependencies has changed from compile to runtime #21507
Comments
Thanks, @michael-simons. This is a side-effect of the build switching to Gradle. If we consider |
I don't want to hijack this issue, However, I noticed other places where something like this happens. Please let me know if I should open a new issue. I noticed that |
Not sure if it is linked to this, but since we updated to 2.3 some of our teammates have the following when running the our maven project from IntelliJ.
Is it possible that the |
@filiphr We can expand the scope of this issue as needed. Where you've noticed the dependencies that are affected, it'd be great if you could comment here with the details please.
No, I don't think so. A change from compile scope to runtime scope will only affect the compile classpath. It should have no effect on runtime behaviour. If you can share a project that reproduces the missing |
Thanks. Currently it is only the one I mentioned before. If we see something else we will let you know.
This is not really easy to reproduce. It sometimes disappears after restarting IntelliJ, reimporting Maven projects several times, etc. It could very much be an IntelliJ bug and how they handle the maven |
I've managed to reproduce the problem with the missing |
The scope of
org.springframework.boot:spring-boot-test
has been changed fromcompile
toruntime
from 2.2.x to 2.3.spring-boot-test
comes as dependency ofspring-boot-test-autoconfigure
.vs
This is a breaking change for library developers providing custom test autoconfiguration. For example, using
SpringBootTestContextBootstrapper
to provide additional properties.SpringBootTestContextBootstrapper
is considered public API:As a workaround I can change the scope back to
compile
again in our Maven build or include the dependency manually, but the change came as a surprise to us.The text was updated successfully, but these errors were encountered: