[
https://issues.apache.org/jira/browse/NIFI-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201304#comment-16201304
]
ASF GitHub Bot commented on NIFI-4444:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2206
I had some trouble getting the cluster configured successfully due to
Zookeeper port conflicts (will be filing a Jira to improve the error messaging
there). I got it working and the flow operates successfully on both branches.
I can't get the toolkit to work, however. Both `notify.sh` and
`node-manager.sh` are reporting errors parsing the `-b` option for the existing
`bootstrap.conf` file, so I will keep playing with that.
Meanwhile, the unit tests and contrib-check all pass on the latest commit.
> Upgrade Jersey Versions
> -----------------------
>
> Key: NIFI-4444
> URL: https://issues.apache.org/jira/browse/NIFI-4444
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Attachments: NIFI-4444.xml
>
>
> Need to upgrade to a newer version of Jersey. The primary motivation is to
> upgrade the version used within NiFi itself. However, there are a number of
> extensions that also leverage it. Of those extensions, some utilize the older
> version defined in dependencyManagement while others override explicitly
> within their own bundle dependencyManagement. For this JIRA I propose
> removing the Jersey artifacts from the root pom and allow the version to be
> specified on a bundle by bundle basis.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
