OK, we are in agreement about removing the $caller then.
I propose that we work on parameterised logging for 2.2 and consider
markers for the next release to achieve a smaller release cycle.
The logging methods will be rewritten to support:
Logger::debug($message); // standard
Logger::debug($m
[
https://issues.apache.org/jira/browse/LOG4PHP-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-110.
--
Resolution: Fixed
Fix Version/s: (was: 2.2)
2.1
The appender has
[
https://issues.apache.org/jira/browse/LOG4PHP-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080983#comment-13080983
]
Christian Grobmeier commented on LOG4PHP-137:
-
v2.1 needs to be available in
[
https://issues.apache.org/jira/browse/LOG4PHP-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Grobmeier updated LOG4PHP-137:
Fix Version/s: (was: 2.1)
2.2
> Improve pear build
> --
The main logging methods (Logger::trace(), Logger::debug(), etc.) currently
take two parameters: $message and $caller.
I traced the path by which the $caller parameter is passed on and it goes
like this:
1. The main logging methods pass it to Logger::log()
2. Logger::log() passes it to Logger::f
