springboot的logback和spring-data-hbase的log4j冲突解决方法

springboot默认的日志框架是logback，它的性能较好，功能强大。选择使用它的时候是默认支持的。但是在springboot里面引入spring-data-hbase（org.springframework.data.hadoop.hbase.HbaseTemplate）的时候，会引入mavendpom.xml的依赖。在hadoop、hbase的依赖里面会引入log4j。springboot在启动的时候感知到classpath里面有Log4j和logback，就会报错。

该如何处理呢？

方案：排除掉log4j的依赖，不能排除的将它转换为 slf4j

参考资料： https://stackoverflow.com/questions/34863719/spring-boot-use-logback-instead-of-log4j

 

there are these three logging frameworks:

• log4j (ancient)
• slf4j (api used everywhere, there are different backends available)
• logback (has nice features and configuration, successor of slf4j)

you have to manually throw out log4j and replace it with the compatibility bridge log4j-over-slf4j.

there is a slf4j backend called logback-classic.

<dependency>
    <!-- legacy log4j ==> slf4j *** 这里是关键 ***-->
    <groupId>org.slf4j</groupId>
    <artifactId>log4j-over-slf4j</artifactId>
    <version>1.7.21</version>
</dependency>
<dependency>
    <!-- slf4j ==> logback 这里也可以不明确的引入logback，因为springboot默认提供 -->
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>1.1.7</version>
</dependency>
<dependency>
    <groupId>...no maintainer...</groupId>
    <artifactId>...old stuff...</artifactId>
    <version>...ancient...</version>
    <exclusions>
        <exclusion>
            <groupId>log4j</groupId>
            <artifactId>log4j</artifactId>
        </exclusion>
        <exclusion>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-log4j12</artifactId>
        </exclusion>
    </exclusions>
</dependency>