[
https://issues.apache.org/jira/browse/KARAF-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021254#comment-13021254
]
Michael Van Geertruy commented on KARAF-560:
--------------------------------------------
Achim,
Thats working as designed. My assumption in coding this was that if a logger
(actually a package name) is specified, then the user only wants to see events
associated with that logger.
If the logger!=null (meaning a package name was passed into the command) but
checkIfFromRequestedLog(event) is false (meaning the event doesn't refer to the
package being logged), then the event does not represent the package the user
wants to see. Hope that makes sense.
> Modify all console log commands to receive a "logger" argument.
> ---------------------------------------------------------------
>
> Key: KARAF-560
> URL: https://issues.apache.org/jira/browse/KARAF-560
> Project: Karaf
> Issue Type: Improvement
> Components: console
> Affects Versions: 3.0.0
> Environment: all
> Reporter: Michael Van Geertruy
> Assignee: Achim Nierbeck
> Fix For: 3.0.0
>
> Attachments: karaf-560-all.txt, karaf-560.txt
>
>
> In log:set and log:get you can specify the logger you want to set and
> retrieve the logging level. This should also be allowed as an argument for
> log:clear, log:display, log:display-exception, and log:tail. If we assume
> users will want to set and get the logging levels of log files other than
> Karaf, we can also assume users will want the rest of the functionality in
> this ticket also.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
