You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by jtstorck <gi...@git.apache.org> on 2016/11/16 22:44:25 UTC

[GitHub] nifi pull request #1237: NIFI-3049 Fixes logging issues due to logback and l...

GitHub user jtstorck opened a pull request:

    https://github.com/apache/nifi/pull/1237

    NIFI-3049 Fixes logging issues due to logback and log4j being on the \u2026

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    
    \u2026classpath
    
    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

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jtstorck/nifi NIFI-3049

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1237.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1237
    
----
commit 2cc5ce2c023fcdf770e05a33bbcfd78c682ff680
Author: Jeff Storck <jt...@gmail.com>
Date:   2016-11-16T22:41:12Z

    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

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1237: NIFI-3049 Fixes logging issues due to logback and log4j be...

Posted by alopresto <gi...@git.apache.org>.
Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/1237
  
    Verified `contrib-check` and all tests pass. Ran TLS toolkit and encrypt-config toolkit and both successfully logged to console. Verified that `NiFiPropertiesLoader` successfully logged to `nifi-app.log` when loading encrypted properties. Verified application smoke tests. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #1237: NIFI-3049 Fixes logging issues due to logback and l...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/nifi/pull/1237


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1237: NIFI-3049 Fixes logging issues due to logback and log4j be...

Posted by alopresto <gi...@git.apache.org>.
Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/1237
  
    Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---