Hi Gary, Can only be done in 3.x since we can't break it in a minor.
Now more on the ecosystem it would also mean dropping or forking JCS from TomEE since TomEE will stay JUL first for its stack and provides a light facade to switch to log4j2 (long story short: it is to avoid to enforce a lib users can not want or to avoid potential conflicts). However reworking the logging in JCS can be interesting, current log usage is slow and sometimes in synchronized blocks so I guess we can be better. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-09-02 19:55 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: > Hi All, > > How about updating JCS from Commons Logging to Log4j 2? > > Gary >
