Bryan Bende created NIFIREG-201:
-----------------------------------
Summary: nifi-registry-extensions impacted by top-level dependency
management
Key: NIFIREG-201
URL: https://issues.apache.org/jira/browse/NIFIREG-201
Project: NiFi Registry
Issue Type: Improvement
Affects Versions: 0.3.0
Reporter: Bryan Bende
Assignee: Bryan Bende
Fix For: 0.3.0
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
