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

Posted to issues@ratis.apache.org by "Shashikant Banerjee (Jira)" <ji...@apache.org> on 2020/04/21 08:00:06 UTC

[jira] [Updated] (RATIS-860) Organize log4j dependency in pom.xml

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

Shashikant Banerjee updated RATIS-860:
--------------------------------------
    Attachment: RATIS-860.000.patch

> Organize log4j dependency in pom.xml
> ------------------------------------
>
>                 Key: RATIS-860
>                 URL: https://issues.apache.org/jira/browse/RATIS-860
>             Project: Ratis
>          Issue Type: Bug
>          Components: build
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.6.0
>
>         Attachments: RATIS-860.000.patch
>
>
> Currently, dependency of log4j in ozone is added as following:
> {code:java}
> <dependency>
>   <groupId>log4j</groupId>
>   <artifactId>log4j</artifactId>
>   <version>1.2.17</version>
> {code}
> Idea here is to add log4j.version as a property in pom.xml and reuse the same while defining the dependency.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)