[
https://issues.apache.org/jira/browse/KARAF-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874454#comment-16874454
]
ASF subversion and git services commented on KARAF-6346:
--------------------------------------------------------
Commit 4c26f330be981fd2073e65427c9d2e3106684966 in karaf's branch
refs/heads/karaf-4.2.x from Freeman Fang
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=4c26f33 ]
[KARAF-6346]Support FATAL level for log console commands
(cherry picked from commit 10842cf0007c355e93c271e5c3e66d492c8c1d25)
> Support FATAL level for log console commands
> --------------------------------------------
>
> Key: KARAF-6346
> URL: https://issues.apache.org/jira/browse/KARAF-6346
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 4.2.6
> Reporter: Emily Berk
> Assignee: Freeman Fang
> Priority: Trivial
> Fix For: 4.3.0, 4.2.7
>
>
> My project uses log4j2. I would like to be able to execute the command
> `log:set FATAL <logger>`.
> *
> https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/command/SetLogLevel.java
> *
> https://github.com/apache/karaf/blob/karaf-4.2.6/log/src/main/java/org/apache/karaf/log/core/Level.java
> *
> https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Level.html
> A work-around is manually editing the org.ops4j.pax.logging.cfg or
> "org.ops4j.pax.logging.log4j2.config.file".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
