You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2017/12/21 19:56:00 UTC

[jira] [Updated] (NIFI-4444) Upgrade Jersey Versions

     [ https://issues.apache.org/jira/browse/NIFI-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Gilman updated NIFI-4444:
------------------------------
    Status: Patch Available  (was: Reopened)

> 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)