[
https://issues.apache.org/jira/browse/NIFI-11765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-11765:
--------------------------------
Fix Version/s: 2.0.0
1.23.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade to apache parent version 30
> -----------------------------------
>
> Key: NIFI-11765
> URL: https://issues.apache.org/jira/browse/NIFI-11765
> Project: Apache NiFi
> Issue Type: Task
> Affects Versions: 1.22.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 2.0.0, 1.23.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There appears to be some weird compatibility issue with apache parent 29 and
> Maven 3.8x and 3.9.x. The scenario that produces the problem is running a
> build with a system property to override a version, say
> "-Dhadoop.version=..." and then some module that does not even reference
> hadoop.version, but does have hadoop dependencies, line ranger stuff which
> uses its own hadoop.version, ends up trying to resolve the version from
> hadoop.version. It happens specifically during the process-remote-resources
> phase:
> {code:java}
> [INFO] --- remote-resources:1.7.0:process (process-resource-bundles) @
> nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> {code}
> There seems to be some significant changes to this apache-jar-resource-bundle
> between 1.4 and 1.5, and apache parent 30 goes to 1.5.
> https://repo1.maven.org/maven2/org/apache/apache/29/apache-29.pom
> https://repo1.maven.org/maven2/org/apache/apache/30/apache-30.pom
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
