GitHub user SpaceLeam edited a comment on the discussion: Deprecate the Log4j Scala API
+1 from me. I recently spent time debugging this API (related to the crash fix I'm currently preparing), and I agree that maintaining parity with the Core safety guarantees seems unnecessarily difficult here. The disconnect between the Java implementation and the Scala wrapper creates edge cases that are hard to catch and maintain. **In fact, while auditing the code for the `traceEntry` fix, I noticed similar "eager evaluation" risks in other public endpoints (e.g., `logMessage`) where the wrapper deviates from the Core's fail-safe logic. Patching these architectural mismatches one by one feels like a whack-a-mole game.** Moving to a native backend for Scala Logging sounds like a much more stable future for users. --- GitHub link: https://github.com/apache/logging-log4j2/discussions/4021#discussioncomment-15424942 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
