[
https://issues.apache.org/jira/browse/NIFI-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5176:
------------------------------
Description:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 9.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 9:
||Issue||Solution||
|Groovy compiler not parsing groovy code correctly on Java 9|Updated
maven-compiler-plugin to 3.7.0, and included dependencies for
groovy-eclipse-compiler:2.9.3-01 and groovy-eclipse-batch:2.4.15-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|hbase-client:1.1.2 depends on jdk.tools:jdk.tools:1.7|Excluded this dependency
*(needs testing)*|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of --add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-plugin not working with Java 10|Switched to gmaven-plus|
was:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 9.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 9:
||Issue||Solution||
|Groovy compiler not parsing groovy code correctly on Java 9|Updated
maven-compiler-plugin to 3.7.0, and included dependencies for
groovy-eclipse-compiler:2.9.3-01 and groovy-eclipse-batch:2.4.15-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|hbase-client:1.1.2 depends on jdk.tools:jdk.tools:1.7|Excluded this dependency
*(needs testing)*|
|nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist|Required addition of --add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.|
> NiFi needs to be buildable on Java 9
> ------------------------------------
>
> Key: NIFI-5176
> URL: https://issues.apache.org/jira/browse/NIFI-5176
> Project: Apache NiFi
> Issue Type: Sub-task
> Reporter: Jeff Storck
> Assignee: Jeff Storck
> Priority: Major
>
> While retaining a source/target comptability of 1.8, NiFi needs to be
> buildable on Java 9.
> The following issues have been encountered while attempting to run a Java
> 1.8-built NiFi on Java 9:
> ||Issue||Solution||
> |Groovy compiler not parsing groovy code correctly on Java 9|Updated
> maven-compiler-plugin to 3.7.0, and included dependencies for
> groovy-eclipse-compiler:2.9.3-01 and groovy-eclipse-batch:2.4.15-01|
> |Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
> needed in TestHL7Query.java|
> |jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
> |hbase-client:1.1.2 depends on jdk.tools:jdk.tools:1.7|Excluded this
> dependency *(needs testing)*|
> |-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
> exist-|-Required addition of --add-modules=jdk.naming.dns
> --add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
> usage of compiling with the --release option (to compile only against public
> APIs in the JDK) from being used. Not an optimal solution.-|
> |groovy-eclipse-plugin not working with Java 10|Switched to gmaven-plus|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
