[jira] [Updated] (NIFI-10926) Exclude jdk.tools when generating extension manifest

["Bryan Bende (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende updated NIFI-10926:
-------------------------------
    Status: Patch Available  (was: Open)

> Exclude jdk.tools when generating extension manifest
> ----------------------------------------------------
>
>                 Key: NIFI-10926
>                 URL: https://issues.apache.org/jira/browse/NIFI-10926
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>             Fix For: nifi-nar-maven-plugin-1.4.0
>
>
> When processing the the dependencies of a NAR to generate the extension-manifest, some Hadoop dependencies have an optional dependency on a system scoped dependency on jdk.tools:
> [https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-annotations/pom.xml]
> If building a NAR with Java 8 that has this transitive dependency, this fails to resolve after upgrading the maven-dependency-tree plugin to version 3.2.0.
> Since this jdk.tools jar was only needed for compiling javadocs in hadoop-common, we can just exclude it from the classpath during our generation of extension-manifest.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)