Hi. Le jeu. 6 févr. 2025 à 12:45, Gary Gregory <garydgreg...@gmail.com> a écrit : > > +1 for JCS-241. A wrapper to the worse logging system is not great IMO.
I've no stake in this, other than support "policy convergence" of all the Commons components. One item in this policy could be: * If logging functionality is needed, use the <logging framework> API. And select the recommended <logging framework>. [IMO too, it makes sense to delegate to "ASF Log4J" rather than continue (hardly) maintaining something else here.] Regards, Gilles > > Gary > > On Thu, Feb 6, 2025, 04:31 Piotr P. Karwasz <pi...@mailing.copernik.eu> > wrote: > > > Hi Thomas, > > > > On 6.02.2025 09:06, Thomas Vandahl wrote: > > > JCS uses java.util.logging by default. To switch to Log4J2, you need the > > system property -Djcs.logSystem=log4j2 > > > See https://commons.apache.org/proper/commons-jcs/UpgradingFrom2x.html > > > > Why do we even use a logging wrapper? I have created JCS-241[1] to > > rewrite the log calls to use Log4j API directly. It should be fairly > > easy to do it using OpenRewrite. > > > > Of course I am not totally unbiased on the choice of the backend to > > keep, but redirecting logs from Log4j API to JUL is trivial, while for > > the other direction you need to setup a `java.util.logging.manager` > > system property or similar. > > > > Piotr > > > > [1] https://issues.apache.org/jira/browse/JCS-241 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
