You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Selvamohan Neethiraj (Jira)" <ji...@apache.org> on 2022/07/08 12:09:00 UTC
[jira] [Commented] (RANGER-3730) log4j dependency is not completely removed
[ https://issues.apache.org/jira/browse/RANGER-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564258#comment-17564258 ]
Selvamohan Neethiraj commented on RANGER-3730:
----------------------------------------------
[~rmani] - I see the commit in 2.3.0 release. Closing this issue as Resolved.
{code:java}
$ git log --grep RANGER-3730
commit ce3339c8ab653d99382caba9b2e5f306a7118561 (HEAD, tag: release-ranger-2.3.0, tag: release-2.3.0-rc3, origin/ranger-2.3)
Author: Kirby Zhou <ki...@gmail.com>
Date: Fri Jun 24 22:51:51 2022 -0700
RANGER-3730: use reload4j to replace log4j-1.2
Signed-off-by: Ramesh Mani <rm...@cloudera.com>
{code}
> log4j dependency is not completely removed
> ------------------------------------------
>
> Key: RANGER-3730
> URL: https://issues.apache.org/jira/browse/RANGER-3730
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Bhavik Patel
> Assignee: kirby zhou
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 0001-RANGER-3730-use-reload4j-to-replace-log4j.patch
>
>
> log4j dependency is present in parent pom file - [https://github.com/apache/ranger/blob/master/pom.xml#L166]
>
> [~madhan] [~ma3mansoori123]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)