[
https://issues.apache.org/jira/browse/NIFI-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308172#comment-16308172
]
ASF GitHub Bot commented on NIFI-4444:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2358
Tested by visiting http://localhost:8080/nifi-api/controller without the
patch applied -- error "The specified resource could not be found". With the
patch applied -- returns expected JSON:
`{"controller":{"id":"b76231af-0160-1000-11f3-3e937575391f","runningCount":0,"stoppedCount":0,"invalidCount":0,"disabledCount":0,"inputPortCount":0,"outputPortCount":0,"siteToSiteSecure":false,"instanceId":"b76231b1-0160-1000-9062-ebe2c82af742","inputPorts":[],"outputPorts":[]}}`
Ran `contrib-check` and all tests pass. +1, merging.
> Upgrade Jersey Versions
> -----------------------
>
> Key: NIFI-4444
> URL: https://issues.apache.org/jira/browse/NIFI-4444
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.4.0
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Fix For: 1.5.0
>
> 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)
