I finally finished what has been consuming me at work for the last month and have some time over this long weekend. I can either go a pick up some Jira issues to work on, continue working on Java 9 support, and/or cut a 2.7 release.
The 2.9 stuff is problematic. The Java team has recommended that we call stackwalker in the first method the caller calls as that would have the lowest overhead. That would mean getting the caller’s location info on every method call in AbstractLogger. I am trying to create a test for that as I suspect it will be too expensive but making the changes to Log4j to implement it is quite extensive. There is probably a better way but I am interested in the overall impact. This really needs to be done asap as Java 9 should be pretty close to being finished and I am afraid the solution they have given us will perform worse than getcallerclass does. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
