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

ASF GitHub Bot commented on NIFI-3692:
--------------------------------------

GitHub user jfrazee opened a pull request:

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

    NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-media bundle to 
resolve org.json cat-x

    Note: We can't remove Twitter4j from nifi-assembly/NOTICE until 
[NIFI-3018](https://issues.apache.org/jira/browse/NIFI-3018) is complete. 

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

    $ git pull https://github.com/jfrazee/nifi NIFI-3692

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

    https://github.com/apache/nifi/pull/1663.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 #1663
    
----
commit 2c3a1215ccee9edd213a55dba0d78a9407b36413
Author: Joey Frazee <[email protected]>
Date:   2017-04-11T15:19:44Z

    NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-media bundle to 
resolve org.json cat-x

----


> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-3692
>                 URL: https://issues.apache.org/jira/browse/NIFI-3692
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Joey Frazee
>            Assignee: Joey Frazee
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

Reply via email to