You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2018/03/06 04:51:00 UTC
[jira] [Created] (NIFI-4936) NiFi parent pom dependency management
forcing versions to align defeating classloader isolation
Joseph Witt created NIFI-4936:
---------------------------------
Summary: NiFi parent pom dependency management forcing versions to align defeating classloader isolation
Key: NIFI-4936
URL: https://issues.apache.org/jira/browse/NIFI-4936
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework, Extensions, Tools and Build
Affects Versions: 1.5.0, 1.4.0, 1.3.0, 1.0.1, 1.2.0, 1.1.0
Reporter: Joseph Witt
Assignee: Joseph Witt
Fix For: 1.6.0
the top level pom in nifi has a massive dependency management section. this was used initially to help enforce consistent usage of dependencies across nifi but this also can defeat the purpose of the classloader isolation offered by nars. We need to push down dependency version declarations to the nar levels where appropriate.
there have been reported issues of defects happening due to us using much newer versions (or sometimes older) of dependencies due to this dependency management model. By pushing declarations down to the proper scope each nar/etc.. can use the specific versions of components it needs and we'll stop introducing issues by forcing a different version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)