Tamas Cservenak created HUDI-7339:
-------------------------------------

             Summary: POM should not redefine Maven Central
                 Key: HUDI-7339
                 URL: https://issues.apache.org/jira/browse/HUDI-7339
             Project: Apache Hudi
          Issue Type: Task
            Reporter: Tamas Cservenak


You latest POM (found 
[here|https://repo.maven.apache.org/maven2/org/apache/hudi/hudi/0.14.0/hudi-0.14.0.pom])
 have several issues:
 * redefines "central" as "Maven Central". There is no need to define Maven 
Central as it comes "out of the box" with Maven
 * adds Cloudera repository group *public* to the build, that is a big no-no, 
as group seems to contain Maven Central proxy. For example, it has 
[junit:junit:4.12|https://repository.cloudera.com/repository/public/junit/junit/4.12/junit-4.12.pom]
 (in fact am unsure WHAT you need from here, as I did not found any *hosted* 
repository that has any content, or is not public. Maybe they need to enable 
anon access to some of their hosted repository, as publishing a group ONLY that 
has Central is a big no-no).
 * adds repository Confluent without any restriction

These should be fixed.



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

Reply via email to