[ 
https://issues.apache.org/jira/browse/NIFI-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672114#comment-15672114
 ] 

ASF subversion and git services commented on NIFI-3049:
-------------------------------------------------------

Commit fa13832a9c07b20e968efc5d8baf7e7e09e1a7b1 in nifi's branch 
refs/heads/master from [~jtstorck]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=fa13832 ]

NIFI-3049 Fixes logging issues due to logback and log4j being on the classpath
Removed logback usage from classpath
Added slf4j-log4j12 dependency in nifi-toolkit pom
Added logback-classic exclusion for nifi-properties-loader used by 
nifi-toolkit-encrypt-config
Updated log4j.properties logging pattern and logger config in 
nifi-toolkit-assembly and nifi-toolkit-zookeeper-migrator, filtering zookeeper 
messages below WARN
Removed logback.groovy since log4j is the single logging implementation
Updated ZooKeeperMigratorMain command line output to match standards 
established by other tools in nifi-toolkit

This closes #1237.

Signed-off-by: Andy LoPresto <alopre...@apache.org>


> ZooKeeper Migrator Toolkit addition has broken logging in NiFI Toolkit and 
> does not provide the correct command line usage output
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-3049
>                 URL: https://issues.apache.org/jira/browse/NIFI-3049
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Tools and Build
>    Affects Versions: 1.1.0
>            Reporter: Jeff Storck
>            Assignee: Jeff Storck
>             Fix For: 1.1.0
>
>
> The ZooKeeper Migrator Toolkit has a dependency on ZooKeeper 3.4.6 which has 
> a hard dependecy on log4j, which conflicts with nifi-property-loader's 
> dependency on logback.  When the toolkit runs, SLF4J finds two logging 
> implementations to bind to and complains, and according to SLF4J's 
> documentation, it is considered random which implementation SLF4J will use.
> The command line output should be modified to adhere to the standard 
> established by the other tools in the toolkit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to