Hi all, Am still getting build failures in regard to atlassion clover/clover2 and apache.org maven-gpg maven, maven-javadoc, maven-source.
In my local repository I have org.apache.maven plugins directory and that contains a bunch of maven plugins but not the problem ones. I downloaded (for each) the jar, pom, and Javadoc files, and dropped them into local directories (3.0.1, 3.2.1, etc). I also checked that com.atlassian.maven.plugins also exists and has a maven-clover2-plugin sub-directory (3.1.11 ). I do not understand why I see these. I gather (from documentation) that the local (.m2) repository gets searched first before heading out to grab things from central. If so, then surely the local versions I stored should be valid. Any help would be gratefully received. Marc From: Marc Hoppins <[email protected]> Sent: Friday, November 26, 2021 12:49 PM To: [email protected] Subject: Again: testing EXTERNAL Hi all, Ambari 2.7.6 was recently released (I assume from the date of the install doc) and I am asking: Why there are errors in locating artifacts/plugins/repositories so soon after release? Clover doesn't appear to be available clover2 as it is now maven-clover-plugin, not clover2, and has been since 4.1.0 - current version 4.1.2. Maven repo still suggests using clover2 which throws an error. Hortonworks references are broken (eg) zookeeper, as they decided to move things around also, and org.apache.maven.plugins also throws errors with missing data with the plugin name/id/artifact id. These seem like simple problems which could have been resolved. Or, is this related to the builders using local repositories which contain many version which have been accumulated over time? How does this help new users try to get to grips with building the tool? Thanks Marc
