[NIFIREG-201] nifi-registry-extensions impacted by top-level dependency management

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3.0
• Fix Version/s: 0.3.0
• Assignee: Bryan Bende
• Reporter: Bryan Bende
• Created: 21/Sep/18 16:10
• Updated: 26/Sep/18 13:46
• Resolved: 26/Sep/18 13:46

Description

While reviewing NIFIREG-200, I noticed that when building with the include-ranger profile, the JARs in ext/ranger/lib ended up being affected by the dependency management section in the root pom.

For example, the versions of Jetty and Jackson JARs were being forced to the versions registry needs, but may not be versions that are compatible with the ranger client.

To deal with this, I propose restructuring the the repository to something like the following:

nifi-registry-core (eveything that used to be at the root, except the assembly and extensions)

nifi-registry-extensions

nifi-registry-assembly

The dependency management can then be moved to the pom of nifi-registry-core so that it does not impact the modules under nifi-registry-extensions.

Issue Links

• links to: GitHub Pull Request #143