Re: [D] Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? [logging-log4j2]
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
Re: [D] Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? [logging-log4j2]
GitHub user ppkarwasz added a comment to the discussion: Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? There will be **no `3.0.0` release of the [Log4j API](https://logging.apache.org/log4j/2.x/manual/api.html)**. This is intentional: both Log4j Core 2 and Log4j Core 3 are designed to use the **same API**, meaning no code changes are required when upgrading to Log4j Core 3. The current release, `3.0.0-beta3`, of Log4j Core is fully compatible with Log4j API version `2.24.x`. To ensure your project always uses the correct API version for Log4j Core 3, we recommend using the [`log4j-bom`](https://logging.apache.org/log4j/3.x/components.html#log4j-bom) for dependency management. ## 📅 Log4j Core 3 Release Timeline Development on the 3.x line began back in 2018, around the same time as the upcoming Jackson 3.x. Since then, the `main` branch has been losing ground and catching up with the `2.x` branch in terms of bug fixes and new features—culminating in `3.0.0-beta3`, which brings us very close to parity. At this point, all planned 3.x features have been delivered. The remaining blocker for the official `3.0.0` release is porting over a final set of changes from `2.x`. As outlined in [my March email](https://lists.apache.org/thread/0jb0gcnddhffywcbfj7o9q3wtbgr1r35), we are currently focused on the `2.25.0` release and do not have the bandwidth to finalize work on 3.x at this time. ## 🙋 How You Can Help We welcome community contributions to help bring `3.0.0` across the finish line. Here’s how you can get involved: ### 🛠️ Port Changes from 2.x to 3.x Issue #3161 lists items that were completed in `2.x` but not yet ported to `main`. While some items (e.g., GraalVM support) are more complex, many are simple cherry-picks. Porting these will bring us closer to a final release. ### 🧪 Test the Beta Releases We've released several `3.x` betas, but user feedback has been limited. Testing these betas and reporting bugs—or even confirming smooth upgrades—would be incredibly valuable. We expect to publish at least one more beta before finalizing `3.0.0`. Your help could significantly accelerate the release. Thanks for being part of the Log4j community! GitHub link: https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13245083 This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [D] Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? [logging-log4j2]
GitHub user garydgregory added a comment to the discussion: Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? And welcome to the pain and confusing we are forcing on our users with this confusing version policy 😞 GitHub link: https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13245251 This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [D] Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? [logging-log4j2]
GitHub user jluehe added a comment to the discussion: Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? @ppkarwasz, we are looking for a Jakarta EE9 compatible version of `org.apache.logging.log4j:log4j-api`. We found that version `2.24.3` is not Jakarta EE9 compatible (as it contains references to `javax` classes), whereas version `3.0.0-beta2` is. That's why we were hoping for a proper `3.0.0` release ... GitHub link: https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13245699 This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [D] Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? [logging-log4j2]
GitHub user jluehe added a comment to the discussion: Timeline for org.apache.logging.log4j:log4j-api:3.0.0 release? Thanks for your response, @ppkarwasz! Yes, the `javax` reference in `Constants.java` is "benign". The problematic reference is here: https://github.com/apache/logging-log4j2/blob/rel/2.24.3/log4j-api/src/main/java/org/apache/logging/log4j/util/Base64Util.java#L45 https://github.com/user-attachments/assets/fa75428b-3911-463b-965b-71e157306225"; /> It is not a compile dependency, but the resulting CNFE in a EE9 environment would impact functionality. GitHub link: https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13254432 This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
