- 07 May, 2020 15 commits
-
-
Phillip Webb authored
Add a test to ensure that a large number of property sources that each contain many items can perform well. See gh-20625
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Spring Buildmaster authored
-
Phillip Webb authored
Remove the recently added slash restriction since Spring Cloud Config Server needs to support names with slashes. See gh-21217
-
Phillip Webb authored
-
Spring Buildmaster authored
-
Stephane Nicoll authored
Closes gh-21352
-
Stephane Nicoll authored
Closes gh-21351
-
Stephane Nicoll authored
Closes gh-21342
-
Stephane Nicoll authored
Closes gh-21349
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-21348
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-21346
-
- 06 May, 2020 25 commits
-
-
Madhura Bhave authored
Closes gh-21344
-
Madhura Bhave authored
Closes gh-21213
-
Madhura Bhave authored
Closes gh-21343
-
Madhura Bhave authored
Prior to this commit, the property was a Boolean with a null default. If it was explicitly set by the user, a context customizer would use that value to set it on the context. However, if it was not set, the default wouldn't be tomcat's default but `false` because it was explicitly set to `false` in `TomcatServletWebServerFactory`. This commit defaults the property itself to `false` so that the default is more obvious to the user. Fixes gh-20796
-
Madhura Bhave authored
-
Phillip Webb authored
Fix the `SystemEnvironmentPropertyMapper.isAncestorOf` implementation to convert names based on their dashed form and to silently ignore any invalid results. Closes gh-14479
-
Andy Wilkinson authored
Closes gh-21341
-
Andy Wilkinson authored
Fixes gh-20759
-
Stephane Nicoll authored
-
Andy Wilkinson authored
The warnings will be addressed by gh-20759. CreateBootStartScripts must be excluded from the classes that are validated by the ValidatePlugins task. It is invalid, but only for Gradle 6.4. gh-20759 will cause it to only be used with Gradle 6.3 and earlier. See gh-21329
-
Stephane Nicoll authored
Closes gh-21340
-
Stephane Nicoll authored
Closes gh-21339
-
Stephane Nicoll authored
Closes gh-21338
-
Stephane Nicoll authored
Closes gh-21337
-
Stephane Nicoll authored
Closes gh-21336
-
Stephane Nicoll authored
Closes gh-21335
-
Stephane Nicoll authored
Closes gh-21334
-
Stephane Nicoll authored
Closes gh-21333
-
Stephane Nicoll authored
Closes gh-21332
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-21331
-
Stephane Nicoll authored
Closes gh-21330
-
Stephane Nicoll authored
Closes gh-21329
-
Andy Wilkinson authored
Closes gh-21327
-
Andy Wilkinson authored
Previously, unlike embedded Jetty, Netty, and Tomcat, Undertow would not stop when one of its worker threads was in use. This meant that a a long-running or stalled request could prevent the application from shutting down in response to SIGTERM or SIGINT, and SIGTERM would be required to get the process to exit. This commit updates the factories for the reactive and servlet Undertow web server factories to configure Undertow to use a 0ms shutdown timeout. This aligns it with the behaviour of Jetty, Netty, and Tomcat. Tests have been introduced to verify the behaviour across the reactive and servlet variants of all four supported embedded web servers. Fixes gh-21319
-