Apache9 commented on pull request #4050:
URL: https://github.com/apache/hbase/pull/4050#issuecomment-1057619529
> how about we get this in place for branches-2 now, so that we can stop
shipping hbase 2 releases with an EOL log4j 1, but we plan for the log4j 2
changes to be the preferred pa
Apache9 commented on pull request #4050:
URL: https://github.com/apache/hbase/pull/4050#issuecomment-1057589064
So do we plan to use reload4j for 2.x, or we plan to directly upgrade to
log4j2?
I plan to backport the log4j2 changes to branch-2 and try to see if using
the old log4j.proper
Apache9 commented on pull request #4050:
URL: https://github.com/apache/hbase/pull/4050#issuecomment-1022859891
> I am testing my Hadoop reload4j patch, and then realized there are a lot
of gotchas when building downstream applications. Please try build HBase
downstream applications with t
Apache9 commented on pull request #4050:
URL: https://github.com/apache/hbase/pull/4050#issuecomment-1018314305
> does it also ban transitive dependencies on log4j and slf4j-log4j12?
Yes, if you do not want to ban transitive dependency, just add
`false`
--
This is an automated mes
