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
Adding spring-security 3.2.0.RC1 dependency to the project prevents application from starting #36
Comments
It works fine with spring-security version 3.1.4.RELEASE |
Maybe there was a package name change for that class between M2 and RC1. Try using the spring-boot-starter-security anyway to protect you from this kind of thing, but we only upgraded to Security 3.2.3.Rc1 on Friday, so your only hope is a snapshot of Boot at this point (M2 coming next week sometime). |
You can also try excluding the SecurityAutoConfiguration
|
Thank you guys! I can live with 3.1.4 + spring-security-javaconfig M1 but wanted to take full advantage of latest java config driven spring security.
helps! |
If you use the starter pom you should get 3.2.0. |
I think this is working now? |
Yes, it does work, checked couple of hours ago. Thanks! |
At the bottom of the document (above the footer), I added links to other guides that readers may find to be useful.
I have a spring-boot driven application that launches embedded Tomcat.
It starts and works fine.
I add the following dependencies to the project (nothing more):
And the application crashes on startup with
Here is the full exception stack:
The text was updated successfully, but these errors were encountered: