EkkoWH commented on issue #3790: URL: https://github.com/apache/logging-log4j2/issues/3790#issuecomment-3023383625
Hello, thank you so much for your warm and thoughtful response! > Could you share a link to the other issue mentioning the resource protocol? I think I might not have expressed myself clearly earlier（It might have been because I used machine translation. ） — the person who previously raised this issue did so in the context of Spring Boot, and unfortunately, it went unanswered. Here is the link to that issue: [https://github.com/spring-projects/spring-boot/issues/37152#issuecomment-2544546256](https://github.com/spring-projects/spring-boot/issues/37152#issuecomment-2544546256) Regarding your suggestion about using `log4j2.component.properties` — you're absolutely right. I revisited the relevant source code today and confirmed that configuring it this way indeed works, and it conveniently eliminates the need to set environment variables manually. I truly appreciate that you're planning to fix this issue! This means that whether we run the application as a JAR or as a native executable, we won’t need any extra configuration — which is fantastic! > In my (not so impartial 😉) opinion, among the logging frameworks supported by the Log4j API, Log4j Core provides the most seamless "out-of-the-box" experience with GraalVM: Finally, I want to clarify that I’m not denying the excellent experience Log4j provides — it’s genuinely great! We've tried other logging frameworks in the past, but Log4j has always been our favorite. I just felt that needing extra configuration when switching from a JAR to a native image somewhat diminished the “out-of-the-box” experience. But of course, that doesn't change how much we appreciate Log4j! I was simply unsure whether my current approach was the right one, which is why I wanted to ask here and learn from your insights. Thank you again for your clarification! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
