Endre Kovacs created NIFIREG-342:
------------------------------------
Summary: streamline nifi-registry docker projects to it's NiFi
counterpart
Key: NIFIREG-342
URL: https://issues.apache.org/jira/browse/NIFIREG-342
Project: NiFi Registry
Issue Type: Task
Affects Versions: 1.0.0
Reporter: Endre Kovacs
Assignee: Endre Kovacs
currently i see a few differences between the layout of NiFi vs.
nifi-registry's docker projects.
# {code}nifi-registry-docker{code} is a child project of
{code}nifi-registry/nifi-registry-core{code} it's NiFi counterpart lives in the
project root. Having it in the project-root is beneficial as it allows us to
defer its execution order after the assembly, so we could leverage the build
artifacts for docker build. Such docker build can be initiated with the
{code}-P docker{code} maven build profile, provided by NIFIREG-252
# currently nifi-registry/nifi-registry-core/nifi-registry-docker/dockerhub is
not a maven project (no pom.xml in its folder) this is another difference
between the NiFi dockerhub and the NiFi Registry counter part.
cc.: [~kdoran]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
