You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2021/12/14 14:41:00 UTC

[jira] [Updated] (NIFI-9483) Evaluate Addition of log4j-to-slf4j

     [ https://issues.apache.org/jira/browse/NIFI-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann updated NIFI-9483:
-----------------------------------
    Summary: Evaluate Addition of log4j-to-slf4j  (was: Evaluate Addition of log4j-slf4j-impl)

> Evaluate Addition of log4j-to-slf4j
> -----------------------------------
>
>                 Key: NIFI-9483
>                 URL: https://issues.apache.org/jira/browse/NIFI-9483
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>
> Several extension components include transitive dependencies on Log4j 2. NiFi uses the SLF4J API for logging in application code, and Logback as the runtime implementation. 
> The Log4j 2 system supports SLF4J for runtime message routing, which would ensure that all log messages route through SLF4J and Logback, as opposed to falling back to the default Log4j 2 appender.  Current extension components should be evaluated to determine whether an explicit dependency on log4j-slf4j-impl is necessary to ensure proper runtime log handling for libraries that rely on the Log4j 2 API.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)