- 03 Aug, 2015 8 commits
-
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Add a "management.health.defaults.enabled" property that controls whether the default health indicators are enabled. This allow to disable them all by default and still enable individual ones using their respective specific property. Closes gh-2298
-
Stephane Nicoll authored
Make `getFaviconLocations` package private so that it's not (wrongly) exposed in the meta-data. Closes gh-3647
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Stephane Nicoll authored
See gh-3405
-
- 02 Aug, 2015 1 commit
-
-
Stephane Nicoll authored
-
- 31 Jul, 2015 7 commits
-
-
Dave Syer authored
See gh-3629
-
Dave Syer authored
Fixes gh-3570
-
Dave Syer authored
Fixes gh-3570
-
Stephane Nicoll authored
Closes gh-3634
-
Stephane Nicoll authored
Closes gh-2575
-
Stephane Nicoll authored
* pr/3632: Fix copyright date
-
arghya88 authored
Closes gh-3632
-
- 30 Jul, 2015 4 commits
-
-
Stephane Nicoll authored
Add an error controller test that translates a ResponseStatus annotated exception that does not contain a reason attribute. See gh-3623
-
Stephane Nicoll authored
Closes gh-3620
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
- 29 Jul, 2015 3 commits
-
-
Stephane Nicoll authored
Make sure that the meta-data can be serialized.
-
Andy Wilkinson authored
Liquibase 3.4.0 contains a bug that causes the initialization of its ServiceLocator to pollute its map of loggers with a DefaultLogger for the logger named "liquibase". Liquibase 3.4.1 contains a change that improves the situation, but does not address is completely. Creating a CustomResolverServiceLocator, as we do, still causes the map of loggers to be polluted due to logging that's performed in ClassLoaderResourceAccessor.getResourcesAsStream. The commit address the problem by upgrading to Liquibase 3.4.1 and adding the package containing our custom logger to the default service locator before we register our custom service locator. This ensures that the logging that's performed during the creation of our custom service locator will still use our custom logger. Closes gh-3470 Closes gh-3616
-
Stephane Nicoll authored
Closes gh-3614
-
- 28 Jul, 2015 6 commits
-
-
Stephane Nicoll authored
Since `ManagementSecurityAutoConfiguration` is cnfiguring web-related things, it has been renamed to `ManagementWebSecurityAutoConfiguration`. Closes gh-2163
-
Stephane Nicoll authored
Currently, the default TemplateResolver had no specific order. Thymeleaf handles that with a "always first" strategy (that can be confusing if several TemplateResolver have a "null" order. While it is a fine default (and changing it could lead to weird side effects), it has to be changed as soon as another TemplateResolver bean is defined in the project. The `spring.thymeleaf.template-resolver-order` property has been added to control the order of the default TemplateResolver. Closes gh-3575
-
Stephane Nicoll authored
* pr/3610: Fix typo
-
arghya88 authored
Closes gh-3610
-
Stephane Nicoll authored
* pr/3608: Fix typos
-
izeye authored
Closes gh-3608
-
- 27 Jul, 2015 10 commits
-
-
Stephane Nicoll authored
-
Stephane Nicoll authored
* pr/3606: Fix typo
-
arghya88 authored
Closes gh-3606
-
Stephane Nicoll authored
* pr/3600: Polish Add locale customization of the ObjectMapper
-
Stephane Nicoll authored
See gh-3600
-
Johannes Stelzer authored
Add a new spring.jackson.locale property to customize the locale of the ObjectMapper. Closes gh-3600
-
Stephane Nicoll authored
-
Pei-Tang Huang authored
Closes gh-3604
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-3601
-
- 26 Jul, 2015 1 commit
-
-
Stephane Nicoll authored
Closes gh-3601
-