You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2020/09/14 15:47:00 UTC

[jira] [Updated] (NIFI-7804) Dependencies ending up in nifi-standard-services-api

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

Joe Witt updated NIFI-7804:
---------------------------
    Fix Version/s: 1.12.1

> Dependencies ending up in nifi-standard-services-api
> ----------------------------------------------------
>
>                 Key: NIFI-7804
>                 URL: https://issues.apache.org/jira/browse/NIFI-7804
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.10.0, 1.11.0, 1.12.0, 1.11.1, 1.11.2, 1.11.3, 1.11.4
>            Reporter: Bryan Bende
>            Priority: Major
>             Fix For: 1.12.1
>
>
> One of the changes in https://issues.apache.org/jira/browse/NIFI-7407 was a refactoring to the SSLContextService interface which added classes from nifi-security-utils. The result is that nifi-standard-services-api-nar now has transitive dependencies of nifi-security-utils included...
> {code:java}
> bcpkix-jdk15on-1.66.jar
> bcprov-jdk15on-1.66.jar
> bcrypt-0.9.0.jar
> bytes-1.3.0.jar
> commons-codec-1.14.jar
> commons-lang3-3.9.jar {code}
> This means any NAR that has a parent of nifi-standard-services-api-nar, which is most of them, now has these on the classpath which may conflict with versions of the same libraries used in the child NAR.
> We should come up with a way to not depend on nifi-security-utils, or split it up into more isolated modules so that these dependencies don't get brought in to the service APIs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)