Hi, Apache POI 5.0.0 uses a dependency on slf4j-api <https://mvnrepository.com/artifact/org.slf4j/slf4j-api> to use slf4j as core logging framework in Apache POI.
It also includes a dependency to jcl-over-slf4j <https://mvnrepository.com/artifact/org.slf4j/jcl-over-slf4j> to redirect logs of third-party libraries that are using commons-logging via slf4j instead. You should be able to either make sure that commons-logging is included first in the classpath or exclude the transitive dependency on jcl-over-slf4j when depending on Apache POI to make sure that commons-logging is used again. BTW, POI 5.1.0 will switch once again to Log4j and depending on commons-logging, so the next release should work better for your use-case again out of the box. Dominik. On Sun, Aug 29, 2021 at 4:20 PM sriram .v <vsrira...@gmail.com> wrote: > We have a multichild project with a parent maven Project. > We have many child project using both commons-logging and POI. Spring boot > project is also using JCL. > So We have conflict with the SLF4J and Commons-logging in class loader > after upgrading POI to 5.0. > What will be the effect if we exclude jcl-over-slf4j. Will POI use > commons-logging without any issues? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@poi.apache.org > For additional commands, e-mail: user-h...@poi.apache.org > >
