17 Commits

Author	SHA1	Message	Date
Spring Operator	7c314122f7	Update build and setup configuration to use HTTPS ... See gh-16243	2019-03-19 16:01:05 +00:00
Spring Buildmaster	5f959b074f	Next Development Version	2016-09-20 20:20:06 +00:00
Spring Buildmaster	a89ef5df6e	Next Development Version	2016-07-28 09:18:40 +00:00
Spring Buildmaster	2216369348	Next Development Version	2016-07-04 14:15:02 +00:00
Spring Buildmaster	819a9574a6	Next Development Version	2016-05-10 05:28:34 +00:00
Spring Buildmaster	376bbe68d8	Next Development Version	2016-05-06 11:23:57 +00:00
Spring Buildmaster	225d877ab9	Next Development Version	2016-02-26 01:06:16 -08:00
Spring Buildmaster	504d3e97ba	Next development version	2016-01-21 18:41:30 -08:00
Spring Buildmaster	8db59059a5	Next Development Version	2015-12-18 05:43:02 -08:00
Spring Buildmaster	3f6f57a80e	Next Development Version	2015-11-16 03:18:54 -08:00
Phillip Webb	a57a88f5cf	Move master to 1.3.0.BUILD-SNAPSHOT	2015-02-26 17:01:02 -08:00
Spring Buildmaster	8f0ad02237	Next development version	2015-02-26 15:26:53 -08:00
Spring Buildmaster	60725cd8bd	Next development version	2015-01-07 23:37:07 -08:00
Phillip Webb	5afd0b4858	Polish sample POM names	2014-12-19 15:59:44 -08:00
Spring Buildmaster	1a788c1741	Next development version	2014-12-10 16:35:50 -08:00
Phillip Webb	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
Dave Syer	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