[ https://issues.apache.org/jira/browse/NIFI-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395325#comment-16395325 ]
ASF subversion and git services commented on NIFI-4936: ------------------------------------------------------- Commit 32a8db22530fa5b3726b6b08f36adf2ffd6cd5c5 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=32a8db2 ] NIFI-4936: - Moving definition of ranger version into root pom. This closes #2532. Signed-off-by: Bryan Bende <bbe...@apache.org> > 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.1.0, 1.2.0, 1.0.1, 1.3.0, 1.4.0, 1.5.0 > Reporter: Joseph Witt > Assignee: Matt Gilman > Priority: Major > Labels: migration > Fix For: 1.6.0 > > Attachments: NIFI-4936.patch, build-fixing, > old-vs-new-dependencies.txt > > > 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)