Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.19.0
-
None
Description
The change in banned dependencies introduced with NIFI-10614 causes Nifi-Registry build to fail with some profiles.
[INFO] --- maven-enforcer-plugin:3.1.0:enforce (enforce-maven-version) @ nifi-registry-ranger-plugin --- [ERROR] Rule 3: org.apache.maven.plugins.enforcer.BannedDependencies failed with message: Found Banned Dependency: org.bouncycastle:bcprov-jdk15on:jar:1.67 Found Banned Dependency: org.bouncycastle:bcpkix-jdk15on:jar:1.67
ozone-client seems to include them transitively:
[INFO] +- org.apache.ozone:ozone-client:jar:1.2.1:compile [INFO] | \- org.apache.ozone:ozone-common:jar:1.2.1:compile [INFO] | +- org.apache.ozone:hdds-common:jar:1.2.1:compile [INFO] | | +- org.bouncycastle:bcpkix-jdk15on:jar:1.67:compile
Profiles used in build:
-Pinclude-ranger,include-atlas,include-hive3,include-rules,include-sql-reporting,include-hadoop-aws,include-hadoop-azure,include-hadoop-cloud-storage,include-hadoop-gcp,include-graph,include-grpc,include-accumulo,include-hadoop-ozone,include-asn1,include-aws,include-snowflake,include-media
Attachments
Issue Links
- relates to
-
NIFI-10691 Duplicated dependencies in nifi-standard-processors pom.xml
- Resolved
- links to