That is something we discussed a while back. There was probably a JIRA for it too. I think simply no one was willing to take on the massive search/replace required. IIRC, Mr Purtell experimented with this and found migration of configuration files to not work as expected.
It would be good to bite the bullet on this for 2.0. We should decide what API we want to assume for the migration -- consume Log4J directly, or go through an abstracted API like SLF4J. That's something I planned to look at after I finish my patch for bumping our version of Yammer/Codahale/Dropwizard metrics. But please, feel free! On Tuesday, November 17, 2015, Heng Chen <[email protected]> wrote: > Some projects begin to use log4j 2.x in my company. > The API for Log4j 2 is not compatible with Log4j 1.x, > So sometimes hbase client log has some conflicts with our project. >
