CONDITIONS EVALUATION REPORT（条件评估报告）

记录一个小问题，相信有很多用spring boot开发的小伙伴都出现过如图一的错误。因为先入为主的因素导致在日志级别为DEBUG级别时，打印了如例2所示的日志，以为是一个报错信息，资讯阅读日志发现是一下系列的匹配流程。

这边简单记录一下解决的方案，如果在没有更换默认日志的情况下，

可以在application.yml配置：

logging:
  level:
    org:
      springframework:
        boot:
          autoconfigure: error  ###可以是info或者error

同样可以在application.properties中配置

logging.level.org.springframework.boot.autoconfigure=error #可以是info或者error

如果更换了日志框架，且恰好为log4j，则可以在log4j.properties中添加一个配置：

log4j.logger.org.springframework.boot.autoconfigure=ERROR

例1：

**************************************
APPLICATION FAILED TO START
***************************************

例2：

============================
CONDITIONS EVALUATION REPORT
============================

Positive matches:
—————–

AopAutoConfiguration matched:
– @ConditionalOnProperty (spring.aop.auto=true) matched (OnPropertyCondition)

AopAutoConfiguration.ClassProxyingConfiguration matched:
– @ConditionalOnMissingClass did not find unwanted class “org.aspectj.weaver.Advice” (OnClassCondition)
– @ConditionalOnProperty (spring.aop.proxy-target-class=true) matched (OnPropertyCondition)

DataSourceAutoConfiguration matched:
– @ConditionalOnClass found required classes “javax.sql.DataSource”, “org.springframework.jdbc.datasource.embedded.EmbeddedDatabaseType” (OnClassCondition)
– @ConditionalOnMissingBean (types: io.r2dbc.spi.ConnectionFactory; SearchStrategy: all) did not find any beans (OnBeanCondition)

DataSourceConfiguration.Generic matched:
– @ConditionalOnProperty (spring.datasource.type) matched (OnPropertyCondition)