Remove logging level changes from devtools
Update `DevToolsPropertyDefaultsPostProcessor` to remove custom logging level configuration. Unfortunately it's not easy to back-off logging overrides when the user has a custom logback/log4j configuration. Closes gh-14310
This commit is contained in:
@@ -59,9 +59,6 @@ public class DevToolsPropertyDefaultsPostProcessor implements EnvironmentPostPro
|
||||
devToolsProperties.put("server.error.include-stacktrace", "ALWAYS");
|
||||
devToolsProperties.put("server.servlet.jsp.init-parameters.development", "true");
|
||||
devToolsProperties.put("spring.reactor.stacktrace-mode.enabled", "true");
|
||||
devToolsProperties.put("logging.level.org.springframework.web", "DEBUG");
|
||||
devToolsProperties.put("logging.level.org.springframework.core.codec", "DEBUG");
|
||||
devToolsProperties.put("logging.level.org.springframework.http", "DEBUG");
|
||||
PROPERTIES = Collections.unmodifiableMap(devToolsProperties);
|
||||
}
|
||||
|
||||
|
||||
@@ -783,13 +783,6 @@ For example, Thymeleaf offers the `spring.thymeleaf.cache` property. Rather than
|
||||
to set these properties manually, the `spring-boot-devtools` module automatically applies
|
||||
sensible development-time configuration.
|
||||
|
||||
Because you need more information about web requests while developing Spring MVC and
|
||||
Spring WebFlux applications, developer tools will enable DEBUG logging for the
|
||||
Spring Framework web infrastructure. This will give you information about the incoming
|
||||
request, which handler is processing it, the response outcome, etc. If you wish to log
|
||||
all request details (including potentially sensitive information), you can turn on
|
||||
the `spring.http.log-request-details` configuration property.
|
||||
|
||||
TIP: For a complete list of the properties that are applied by the devtools, see
|
||||
{sc-spring-boot-devtools}/env/DevToolsPropertyDefaultsPostProcessor.{sc-ext}[DevToolsPropertyDefaultsPostProcessor].
|
||||
|
||||
|
||||
Reference in New Issue
Block a user