[
https://issues.apache.org/jira/browse/KARAF-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558106#comment-17558106
]
ASF GitHub Bot commented on KARAF-7423:
---------------------------------------
i-thiemann commented on PR #1536:
URL: https://github.com/apache/karaf/pull/1536#issuecomment-1164459005
Using the configuration adaptation internally revealed a bug, where
creation logger could not work if the last element of the configuration xml had
child elements. This is now fixed
> Add logback configuration option
> --------------------------------
>
> Key: KARAF-7423
> URL: https://issues.apache.org/jira/browse/KARAF-7423
> Project: Karaf
> Issue Type: Improvement
> Reporter: Ian Thiemann
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> Since the log4j vulnerability of last year we've been having trouble using
> karaf logging in some systems that exclude vulnerable versions of log4j as a
> security policy. Even if log4j is not used as a logger, the configuration
> syntax of it is used, which requires including the log4j jar.
> We would like to have the option of using logback configuration as an added
> alternative to log4j, so that we can use the logging functionality on secure
> systems that exclude log4j.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
