- 27 Nov, 2019 1 commit
-
-
Madhura Bhave authored
In general we do not recommend using @PropertySource due to them being added to the environment too late for auto-configuration to use them. This commit updates the documentation to mention them in the list of external sources along with a note. Closes gh-18900
-
- 26 Nov, 2019 1 commit
-
-
Madhura Bhave authored
Closes gh-19026
-
- 25 Nov, 2019 14 commits
-
-
Stephane Nicoll authored
Closes gh-19124
-
Stephane Nicoll authored
Closes gh-19123
-
Stephane Nicoll authored
Closes gh-19122
-
Stephane Nicoll authored
Closes gh-19121
-
Stephane Nicoll authored
Closes gh-19120
-
Stephane Nicoll authored
Closes gh-19119
-
Stephane Nicoll authored
Closes gh-19118
-
Stephane Nicoll authored
Closes gh-19117
-
Stephane Nicoll authored
Closes gh-19116
-
Stephane Nicoll authored
Closes gh-19115
-
Stephane Nicoll authored
Closes gh-19114
-
Stephane Nicoll authored
* pr/19109: Polish "Use ssl.enabled flag when RabbitMQ address has no protocol" Use ssl.enabled flag when RabbitMQ address has no protocol Closes gh-19109
-
Stephane Nicoll authored
There is a direct link between the sslEnabled flag and the default port that should be used by an address. The checks are currently set in two places: * Determine which port should be used * Determine if SSL should be enabled This commit polishes the initial proposal so that secureConnection is only set if a protocol is available. See gh-19109
-
cbono authored
See gh-19109
-
- 22 Nov, 2019 2 commits
-
-
Stephane Nicoll authored
* pr/18873: Let Liquibase smoke test pass on non-english systems Closes gh-18873
-
dreis2211 authored
See gh-18873
-
- 21 Nov, 2019 5 commits
-
-
Stephane Nicoll authored
* pr/19057: Remove invalid example of spring.mvc.async.request-timout property Closes gh-19057
-
Adam Michalik authored
See gh-19057
-
Stephane Nicoll authored
* pr/19027: Polish "Fix logging in CloudFoundryVcapEnvironmentPostProcessor" Fix logging in CloudFoundryVcapEnvironmentPostProcessor Closes gh-19027
-
Stephane Nicoll authored
See gh-19027
-
Mark Bigler authored
See gh-19027
-
- 20 Nov, 2019 4 commits
-
-
Stephane Nicoll authored
See gh-19072
-
Stephane Nicoll authored
See gh-19068
-
Stephane Nicoll authored
See gh-19051
-
Stephane Nicoll authored
See gh-19068
-
- 19 Nov, 2019 3 commits
-
-
Madhura Bhave authored
Fixes gh-18908
-
Madhura Bhave authored
-
Madhura Bhave authored
Fixes gh-18998
-
- 16 Nov, 2019 2 commits
-
-
Stephane Nicoll authored
* pr/19028: Fix syntax error in configuration metadata sample in docs Closes gh-19028
-
dreis2211 authored
See gh-19028
-
- 13 Nov, 2019 4 commits
-
-
Madhura Bhave authored
* pr/19008: Fix build badge in README Closes gh-19008
-
dreis2211 authored
See gh-19008
-
Madhura Bhave authored
* pr/19003: Consistently use task timeout in CI pipeline Closes gh-19003
-
dreis2211 authored
See gh-19003
-
- 12 Nov, 2019 1 commit
-
-
Stephane Nicoll authored
-
- 08 Nov, 2019 2 commits
-
-
Andy Wilkinson authored
Closes gh-18842
-
Andy Wilkinson authored
Previously, when RunProcess handled a SIGINT it would immediately attempt to destroy the process that it had run. This created a race condition between the SIGINT being handled by the child process and RunProcess destroying the child. The exact behavior of destroy is implementation dependent and it may result in forcible termination of the process where shutdown hooks are not called. This is what happens on Windows. The exit code in such a case is 1 which prevents anything from waiting for the process to complete from detecting that it ended as a result of a SIGINT, leaving it with no choice but to report an error. This is what happens with mvn spring-boot:run with a forked process on Windows and results in the build failing. This commit updates RunProcess to allow the child process to handle the SIGINT itself, waiting for up to five seconds for that to happen before the process is then destroyed. Given this time, the child process exits with 130 which RunMojo already handles correctly as indicating that the process died due to SIGINT and the build completes with success as a result. Fixes gh-18936
-
- 07 Nov, 2019 1 commit
-
-
Andy Wilkinson authored
Previously, whitespace in between the keys and values in the JSON was not trimmed correctly in BasicJsonParser which lead to it incorrectly parsing JSON with whitespace between the opening of a list ([) and the opening of a map ({). This commit updates the parser to trim unwanted whitespace and adds a test to AbstractJsonParserTests to verify the whitespace handling behaviour across all JsonParser implementations. Closes gh-18911
-