[
https://issues.apache.org/jira/browse/CALCITE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CALCITE-4858:
------------------------------------
Labels: pull-request-available (was: )
> Use Log4j2 instead of unsupported Log4j (1.x) in tests
> ------------------------------------------------------
>
> Key: CALCITE-4858
> URL: https://issues.apache.org/jira/browse/CALCITE-4858
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.28.0
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.29.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the logger implementation (for SL4J APIs) that is used in tests is
> Log4j (1.x) via slf4j-log4j12 dependency. Log4j (1.x) has reached [end of
> life in
> 2015|https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces]
> and using it is highly discouraged for multiple reasons (security,
> performance, features, etc.)
> {noformat}
> 5 August 2015 --The Apache Logging Services™ Project Management Committee
> (PMC) has announced that the Log4j™ 1.x logging framework has reached its end
> of life (EOL) and is no longer officially supported.
> {noformat}
> The goal of this JIRA is to use the more modern Log4j2 as the chosen
> implementation for the SLF4J APIs (via log4j-slf4j-impl) in tests. The only
> modules that cannot benefit from this upgrade are Pig/Piglet due to tight
> dependencies to log4j API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
