On 14.02.2017 22:57, Ceki Gülcü wrote:
Hi Dalibor, Thank you for the useful pointer to a possible workaround. The issue impacting the slf4j-log4j12 module (which relies on log4j 1.2.17) is now fixed. The fix will ship with release 1.7.23 of SLF4J. See also https://jira.qos.ch/browse/SLF4J-393
Thanks, Ceki - great to hear you could make the concept in the workaround proposed in the Log4j 1.x EOL blog work for your use case as well.
cheers, dalibor topic -- <http://www.oracle.com> Dalibor Topic | Principal Product Manager Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961 <tel:+491737185961> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
