Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix reference to AutoConfigurationReportLoggingInitializer in docs

Browse Source 
Closes gh-11026
This commit is contained in:
Stephane Nicoll
2017-11-15 09:14:01 +01:00
parent 5f5e7e5089
commit 370453c765
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View File

@@ -74,10 +74,10 @@ NOTE: Spring Boot provides numerous `FailureAnalyzer` implementations, and you c
<<howto.adoc#howto-failure-analyzer,add your own>>.
If no failure analyzers are able to handle the exception, you can still display the full
auto-configuration report to better understand what went wrong. To do so, you need to
conditions report to better understand what went wrong. To do so, you need to
<<boot-features-external-config,enable the `debug` property>> or
<<boot-features-custom-log-levels,enable `DEBUG` logging>> for
`org.springframework.boot.autoconfigure.logging.AutoConfigurationReportLoggingInitializer`.
`org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener`.
For instance, if you are running your application by using `java -jar`, you can enable
the `debug` property as follows:

2
spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
View File

@@ -454,7 +454,7 @@ add your own `DataSource` bean, the default embedded database support backs away
If you need to find out what auto-configuration is currently being applied, and why,
start your application with the `--debug` switch. Doing so enables debug logs for a
selection of core loggers and logs an auto-configuration report to the console.
selection of core loggers and logs a conditions report to the console.