On 14.02.2017 12:14, Ceki Gülcü wrote:
In the context of SLF4J, the build of the slf4j-log4j12 module fails
since log4j can no longer correctly detect the version of Java and shuts
down MDC support. In short, the changes introduced in JEP 223 have
significant consequences for log4j 1.2.x and by ricochet for SLF4J.
Hi Ceki,
general information about Log4J 1.x on JDK9 can be found at
https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 .
In particular, the blog points to a potential workaround for Log4j 1.x,
although, of course, migrating off libraries that are no longer
maintained should be the preferred choice for most developers.
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
