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

David Handermann updated NIFI-9483:
-----------------------------------
    Description: 
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-to-slf4j is necessary to ensure proper runtime log handling for libraries 
that rely on the Log4j 2 API.

  was:
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.


> 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-to-slf4j 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)

Reply via email to