ed1ce140c0
Next Development Version
2017-01-26 14:20:39 +00:00
9057f9ae1f
Next development version
2016-12-23 00:15:23 +00:00
e712a9ba8c
Next Development Version
2016-11-08 16:55:37 +00:00
6bd670edbc
Initiate 1.4.x branch
2016-09-21 11:11:24 +02:00
334baaeffd
Next development version
2016-07-28 19:54:01 +00:00
fbaf209240
Move master to 1.4.0.BUILD-SNAPSHOT
2016-01-24 10:45:24 -08:00
504d3e97ba
Next development version
2016-01-21 18:41:30 -08:00
8db59059a5
Next Development Version
2015-12-18 05:43:02 -08:00
3f6f57a80e
Next Development Version
2015-11-16 03:18:54 -08:00
a57a88f5cf
Move master to 1.3.0.BUILD-SNAPSHOT
2015-02-26 17:01:02 -08:00
8f0ad02237
Next development version
2015-02-26 15:26:53 -08:00
60725cd8bd
Next development version
2015-01-07 23:37:07 -08:00
5afd0b4858
Polish sample POM names
2014-12-19 15:59:44 -08:00
1a788c1741
Next development version
2014-12-10 16:35:50 -08:00
6634af6a25
Fix broken parent POM version
...
Update the parent POM version in spring-boot-sample-web-secure-custom
2014-08-12 13:45:19 -07:00
0cf1c6f0e5
Refactor AuthenticationManagerConfiguration to make sure it works
...
if user also adds @EnableWebMvcSecurity. The problem is that the ordering
of the init() and configure() methods in the Spring Security configurers
can force things to happen too early unless we are careful. It's still a bit
twitchy I would say, but this relatively small change seems to fix the GS guide
and not break any existing tests.
I added a sample which mimic ths GS guide so we get an integration test that
executes the new code paths.
Fixes gh-1364
2014-08-11 17:42:30 -07:00
Spring Buildmaster
Stephane Nicoll
Phillip Webb
Dave Syer