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

Posted to dev@ranger.apache.org by "Bhavik Patel (Jira)" <ji...@apache.org> on 2022/06/23 11:44: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=17558025#comment-17558025 ] 

Bhavik Patel commented on RANGER-3730:
--------------------------------------

master branch commit link: https://github.com/apache/ranger/commit/c1e577ce8e401525711c391dbfffacb8ce20daba 

> 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
>         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.7#820007)