You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2023/06/29 14:01:00 UTC
[jira] [Created] (NIFI-11765) Upgrade to apache parent version 30
Bryan Bende created NIFI-11765:
----------------------------------
Summary: 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
Fix For: 1.latest, 2.latest
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)