[NIFI-4936] NiFi parent pom dependency management forcing versions to align defeating classloader isolation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0, 1.2.0, 1.0.1, 1.3.0, 1.4.0, 1.5.0
• Fix Version/s: 1.6.0
• Component/s: Core Framework, Extensions, Tools and Build
• Labels: migration
• Assignee: Matt Gilman
• Reporter: Joe Witt
• Created: 06/Mar/18 04:50
• Updated: 12/Mar/18 14:41
• Resolved: 12/Mar/18 14:41

Description

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.

Issue Links

• links to: GitHub Pull Request #2512
• links to: GitHub Pull Request #2532