would there be value in refactoring out log4j completely and just using JUL? is POI actually leveraging any exotic features of log4j or is this a leftover from the days before JUL existed?
Stanton Fisque principal technologist latticeware.com portland, oregon > On Nov 14, 2024, at 12:44 PM, PJ Fanning <fannin...@yahoo.com.INVALID> wrote: > > I'm going to suggest that we create a new POI LogManager that wraps the log4j > one. This would catch null loggers and log4j exceptions and replace them with > a no-op logger instance. We can print to system.err to notify that we have > done this. > > I don't think log4j issues should allowed to make POI fail completely. I'm > afraid that we have to assume that log4j is not reliable. > > Reading > * https://github.com/apache/logging-log4j2/issues/3196 > * https://lists.apache.org/thread/2fpkq93hvdz5ox8w6cqt7sbjrc0x66z6 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
