[nifi] branch main updated: NIFI-10182 Removed optional vendor Maven repository

[pv...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pvillard pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi.git


The following commit(s) were added to refs/heads/main by this push:
     new f3455372bd NIFI-10182 Removed optional vendor Maven repository
f3455372bd is described below

commit f3455372bd6981cfe8b1f4c8fabb6426a8dbef75
Author: exceptionfactory <ex...@apache.org>
AuthorDate: Wed Jun 29 15:16:50 2022 -0500

    NIFI-10182 Removed optional vendor Maven repository
    
    Signed-off-by: Pierre Villard <pi...@gmail.com>
    
    This closes #6169.
---
 pom.xml | 25 -------------------------
 1 file changed, 25 deletions(-)

diff --git a/pom.xml b/pom.xml
index a80f86f912..70c3d0b36b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1089,31 +1089,6 @@
                 </dependencies>
             </dependencyManagement>
         </profile>
-        <!-- The following profiles are here as a convenience for folks that
-            want to build against vendor-specific distributions of the various Hadoop
-            ecosystem libraries. These will alter which dependencies are sourced in a
-            manner that can adjust the correct LICENSE and NOTICE requirements for any
-            affected jar and the resulting assembly overall. These L&N impacts are not
-            automatically handled by the build process and are the responsibility of
-            those creating and using the resulting binary artifacts. -->
-        <profile>
-            <!-- This profile will add the Cloudera repository for resolving
-                Cloudera Distribution of Hadoop (CDH) artifacts for the Hadoop bundles -->
-            <id>cloudera</id>
-            <repositories>
-                <repository>
-                    <id>cloudera-repo</id>
-                    <name>Cloudera Repository</name>
-                    <url>https://repository.cloudera.com/artifactory/cloudera-repos</url>
-                    <releases>
-                        <enabled>true</enabled>
-                    </releases>
-                    <snapshots>
-                        <enabled>false</enabled>
-                    </snapshots>
-                </repository>
-            </repositories>
-        </profile>
         <profile>
             <!-- Run "mvn validate -P dependency-check" to generate dependency-check-report.html in the target directory -->
             <!-- Report results require detailed analysis to determine whether the vulnerability impacts the application -->