[
https://issues.apache.org/jira/browse/NIFIREG-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345088#comment-16345088
]
ASF GitHub Bot commented on NIFIREG-120:
----------------------------------------
Github user kevdoran commented on the issue:
https://github.com/apache/nifi-registry/pull/89
Thanks @abinet and @Chaffelson. Will review.
@apiri and @bbende, I looked into the comment above about the jdk and the
error log @Chaffelson provided. It looks like a requirement for jdk/javac got
introduced due to a Java language in a DB migration script:
[V1.3__DropBucketItemNameUniqueness.sql#L16](https://github.com/apache/nifi-registry/blob/master/nifi-registry-framework/src/main/resources/db/migration/V1.3__DropBucketItemNameUniqueness.sql#L16).
This script gets compiled and executed at runtime during app startup in order
to initialize (if necessary) the embedded H2 database. Not sure what we want to
do about that, if anything, just mentioning it.
> Basic Docker Image
> ------------------
>
> Key: NIFIREG-120
> URL: https://issues.apache.org/jira/browse/NIFIREG-120
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Daniel Chaffelson
> Priority: Minor
> Fix For: 0.2.0
>
>
> It would be convenient if NiFi Registry had an integrated Docker image ready
> for uploading to Dockerhub, similar to the main NiFi Project, for ease of
> integration testing.
> This could probably be ported, with some changes, from the same approach used
> in the main NiFi project for continuity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
