[
https://issues.apache.org/jira/browse/NIFI-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462726#comment-17462726
]
ASF subversion and git services commented on NIFI-9483:
-------------------------------------------------------
Commit 9dd6b5f3e5fb7b2cfeab3a9b174132344a17db85 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9dd6b5f ]
NIFI-9483 This closes #5616. Excluded Log4j 2 log4j-core and related libraries
- Added log4j-core to list of banned dependencies
- Added log4j-to-slf4j for Elasticsearch 5 processors to support runtime logging
Signed-off-by: Joe Witt <[email protected]>
> 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
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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)
