- 19 Dec, 2013 18 commits
-
-
Spring Buildmaster authored
-
Dave Syer authored
-
Christian Dupuis authored
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
Change JmxAutoConfiguration so that by default JMX exposure is not enabled. This matches the Javdoc text.
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
-
- 18 Dec, 2013 8 commits
-
-
Christian Dupuis authored
Change strategy from ApplicationListener to SmartLifecycle to avoid multiple registration attempts for the same beans When running with parent/child application contexts the previous implementation was trying to re-register the same beans with JMX which led to errors.
-
Christian Dupuis authored
-
Phillip Webb authored
Reinstate initializeWithSensibleDefaults() on AbstractLoggingSystem beforeInitialize(). This is required to ensure no superfluous logging output occurs when starting up a spring boot application from the command line. It appears that commit e9c649df modified the logic in an attempt to prevent double initialization. fixes gh-174
-
Christian Dupuis authored
-
Christian Dupuis authored
Actuator endpoints are now being exposed over JMX.
-
Phillip Webb authored
Filter duplicate class names when loading spring.factories files. The prevents errors if -source jars are included on the classpath. fixes gh-161
-
Dave Syer authored
-
Phillip Webb authored
-
- 17 Dec, 2013 8 commits
-
-
Dave Syer authored
Spring Security 3.2 has a new annotation @EnableWebMvcSecurity that we should use if MVC is being used.
-
Dave Syer authored
-
Dave Syer authored
-
Dave Syer authored
Fixes gh-146
-
Dave Syer authored
-
Dave Syer authored
Now it can parse nested lists as map values. Fixes gh-169
-
Dave Syer authored
Fixes gh-168
-
Dave Syer authored
-
- 16 Dec, 2013 6 commits
-
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
Remove system properties when testing strict property binding. This prevents test failures that can occur if the local environment happens to have certain environment variables defined.
-
Dave Syer authored
As discussed in gh-162
-
johnou authored
-
Dave Syer authored
-