- 20 Oct, 2017 12 commits
-
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Closes gh-8899
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-7999
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-10709
-
Stephane Nicoll authored
* pr/10700: Polish
-
Johnny Lim authored
Closes gh-10700
-
Stephane Nicoll authored
See gh-10671
-
Madhura Bhave authored
-
- 19 Oct, 2017 9 commits
-
-
Madhura Bhave authored
Following some changes in the latest snapshot this includes: - Some updates to oauth2 client auto-config - Security auto-config no longer relies on GlobalAuthenticationConfigurerAdapter - Remove reactive security starter Closes gh-10704
-
Madhura Bhave authored
Closes gh-10671
-
Madhura Bhave authored
Regardless of whether the web endpoints have been enabled or not, all endpoints for which beans are created need to be exposed in a CF environment under /cloudfoundryapplication. Closes gh-10673
-
Stephane Nicoll authored
Closes gh-10684
-
Stephane Nicoll authored
-
Andy Wilkinson authored
This commit introduces a new mainClassName property on the springBoot DSL provided by the Gradle plugin. It can be used to explicitly configure the mainClassName of the default bootRun, bootJar, and bootWar tasks in a single place. Previously, the only mechanism provided to do so was the mainClassName property that's only available when the application plugin has been applied. Closes gh-10623
-
Andy Wilkinson authored
Previously, BootRun used the main property to configure the name of the main class to run while BootJar and BootWar used the mainClass property. Both were different to the application plugin which provides a mainClassName project property. This commit updates BootRun, BootJar, and BootWar to change the name of the property used to configure the name of the main class to be mainClassName. This makes the three Boot-specific tasks consistent with each other, and also aligns them with Gradle's own application plugin. Closes gh-10622
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-10691
-
- 18 Oct, 2017 11 commits
-
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-10687
-
Madhura Bhave authored
Closes gh-10526
-
Brian Clozel authored
See gh-10679
-
Andy Wilkinson authored
Closes gh-10678
-
Andy Wilkinson authored
Closes gh-10677
-
Andy Wilkinson authored
Closes gh-10676
-
Andy Wilkinson authored
Closes gh-10675
-
Andy Wilkinson authored
Closes gh-10674
-
Stephane Nicoll authored
* pr/10670: Polish HttpHeaderInterceptor
-
dreis2211 authored
Closes gh-10670
-
- 17 Oct, 2017 8 commits
-
-
Andy Wilkinson authored
Closes gh-10477
-
Andy Wilkinson authored
Previously, we relied on Mockito's internals to bypass any Spring AOP proxy during verification of a spy. Thanks to a new API in Mockito, we can replace the use of Mockito's internals with a VerificationStartedListener. This listener changes Mockito's view of the mock to be the ultimate target of the AOP proxy, i.e. to be the actual Mockito-created spy, allowing Mockito's verification of the spy to proceed successfully. This above-described change will mean that we require a very up-to-date version of Mockito so the tests that verify our compatibility with 2.5 have been removed as we will no longer support it when using @MockBean or @SpyBean. Lastly, two tests have been updated to replace their usage of the internal MockUtil class with the equivalent public API calls. Closes gh-10352
-
Andy Wilkinson authored
Closes gh-10668
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Closes gh-10666
-
Stephane Nicoll authored
Closes gh-10647
-
Stephane Nicoll authored
* pr/10657: Remove "Securing the H2 console" section
-
Johnny Lim authored
Closes gh-10657
-