[
https://issues.apache.org/jira/browse/NIFI-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521177#comment-17521177
]
Gregory M. Foreman commented on NIFI-9656:
------------------------------------------
My client has custom nar's that rely on Java 11 jar libraries. Addressing this
issue would simplify deployments for us. If it is trivial to do two images
during the deployment, it would be appreciated. Additionally, Nifi 1.16 now
supports Java 17 (NIFI-9280), so having Java 8, 11, and 17 images would be even
better.
> Publish an alternative Java 11 docker image
> -------------------------------------------
>
> Key: NIFI-9656
> URL: https://issues.apache.org/jira/browse/NIFI-9656
> Project: Apache NiFi
> Issue Type: Wish
> Components: Docker
> Affects Versions: 1.15.3
> Environment: Docker
> Reporter: Christoph Nölle
> Priority: Minor
>
> There have been requests before to update the official Docker image to Java
> 11 (such as [NIFI-9188|https://issues.apache.org/jira/browse/NIFI-9188]). As
> I understand, this would be a breaking change for many users, though, and
> therefore has been postponed for Nifi 2.0. On the other hand, it would be
> quite desirable if one could use Java 11 features in custom processors
> (without maintaining a custom Docker image).
> A solution could be to keep Java 8 for the default image (e.g. tagged
> "1.15.3" = latest) and provide a second image, e.g. "1.15.3-openjdk-11". The
> Dockerfile has already been adapted to support building with a Java 11 base
> image in [https://github.com/apache/nifi/pull/4460].
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
