GitHub user ppkarwasz added a comment to the discussion: Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release?
Thank you for the clarification. As far as I’m aware, the Log4j API itself doesn’t directly depend on Java EE 8 or Jakarta EE 9 APIs. Could you point to the specific usage or class reference you’re seeing that causes compatibility issues? One area that may be causing confusion is the use of the `Servlet` class in a heuristic used to determine if the application is running in a web environment. This is part of setting the default value for the `log4j2.isWebapp` system property: https://github.com/apache/logging-log4j2/blob/2bc484c30d7ca52606ccd185584acf513417a755/log4j-api/src/main/java/org/apache/logging/log4j/util/Constants.java#L44-L47 This is not a hard dependency — Log4j checks for the presence of the `Servlet` class reflectively and does not require it at runtime. You can find more details about this behavior in the documentation for [`log4j2.isWebapp`](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.isWebapp). If you’ve found a different kind of reference to `javax.*` packages that breaks Jakarta EE 9 compatibility, I’d appreciate a pointer to the exact code or context. GitHub link: https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13249838 ---- This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
