You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (Jira)" <ji...@apache.org> on 2020/10/31 10:32:00 UTC

[jira] [Resolved] (ACCUMULO-3641) Mark slf4j implementation dependencies "optional"

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

Christopher Tubbs resolved ACCUMULO-3641.
-----------------------------------------
    Resolution: Not A Problem

This looks done in current code.

> Mark slf4j implementation dependencies "optional"
> -------------------------------------------------
>
>                 Key: ACCUMULO-3641
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3641
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Christopher Tubbs
>            Priority: Major
>
> After ACCUMULO-1242 is complete, we should not have any more direct usage of log4j or any other particular slf4j implementation. As such, we should mark log4j (and any other slf4j implementations) as optional in the dependencies section of the POM.
> ["Optional" dependencies in Maven|http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html] are not automatically inherited transitively when other projects depend on ours. This is important, because if somebody writes a client application which depends on Accumulo code, we should not be forcing that application into a particular logging implementation. Marking it optional is preferable to forcing them to exclude the transitive dependencies in order to provide their own. It will also prevent conflicts when they have dependencies on other projects, which require a particular conflicting implementation of slf4j.



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