jengebr commented on PR #2593: URL: https://github.com/apache/logging-log4j2/pull/2593#issuecomment-2127237324
Responding to a few details: > As far as making log4j-api lighter goes.... Using the size of the jar file is meaningless. It could be 1TB but if you are only using 1 class from it that is all that is going to be loaded. Spring and Tomcat both scan the entire classpath to look for annotated classes, and more classes translate into a slower scan. However, moving classes from one library to another is neutral in this regard. > Yes, I understand ThreadContextMap isn't going away. It can't as long as SLF4J is supported. But I really dislike the efforts to "fix" it. Improving library implementations with no application change is a clear win, since it's effectively a free improvement to every application. I'm not sure if that's what you mean by "fix"? -- 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
