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

Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/03/28 12:55:41 UTC

[jira] [Updated] (NIFI-3097) Investigate explicit dependencies on logging implementations (logback, log4j)

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

Joseph Witt updated NIFI-3097:
------------------------------
    Fix Version/s:     (was: 1.2.0)

> Investigate explicit dependencies on logging implementations (logback, log4j)
> -----------------------------------------------------------------------------
>
>                 Key: NIFI-3097
>                 URL: https://issues.apache.org/jira/browse/NIFI-3097
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Core Framework, Extensions, Tools and Build
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Jeff Storck
>
> Ideally NiFi, the extensions, and the Toolkit, would have dependencies on SLF4J, and only a single logging implementation would be provided at runtime.  Currently, log4j and logback end up on the runtime classpath due to transitive, and in some cases explicit, dependencies.  This causes issues, specifically with the Toolkit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)