Thanks, I shall look at that later. Let’s get with one thing at a time. My knowledge of JIRA is only slightly better than that of Ambari.
Marc From: Matt Andruff <matt.andr...@gmail.com> Sent: Saturday, January 15, 2022 2:19 PM To: user@ambari.apache.org Subject: Re: Inconsistencies and queries EXTERNAL Hey Marc, You are posting some dev questions to the user thread. You may not get a large response posting those questions here. This is an open source project and well staffed by volunteers. You can volunteer your time to this project to help fix the pieces of it that you find frustrating. Wouldn't we all like more documentation? Have you considered looking at jira for this project to see what work is planned? It might be a good place for you to help contribute. I do know that Bigtop has done work to create an Ambari build that runs on Bigtop not hdp. You might want to look at that project. But Bigtop's documentation isn't any better than what's here so please come willing to help make it better. You get more bees with honey than vinegar. On Fri., Jan. 14, 2022, 06:58 Marc Hoppins, <marc.hopp...@eset.com<mailto:marc.hopp...@eset.com>> wrote: HI all, Yesterday I was gtting “failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec” Errors. A new day today, I did a mvn clean, removed my .m2/repository directory, re-run (ambari top-level) mvn versions:set -DnewVersion=2.7.6.0.0 and again in ambari-metrics directory, then finally run mvn -B clean install jdeb:jdeb -DnewVersion=2.7.6.0.0 -DbuildNumber=388e072381e71c7755673b7743531c03a4d61be8 -DskipTests -Dpython.ver="python >= 2.6" and now I am getting “failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:yarn” So, my question (for today): what can cause failure one day with one plugin but different failure the next day with a different plugin when nothing in any of the POM files has changed? For the record, I also blitzed my virtual setup and have a clean Ubuntu18 install with openjdk-8 (1.8.0_312) and maven 3.8.4. Thus, I am following the official (?) documented install/.build instructions. In regard to the project/tool there is nothing in the way of troubleshooting the build process, no hint or otherwise of what could require checking/changing other than the note about http repository blocking. Given that Ambari is heavily reliant on HDP, and those repositories only cater for <=Centos7 and <=Ubuntu18, what plans (if any) do the project team have for 1. Moving away from reliance on HDP/Cloudera 2. Improving documentation or video guides Thanks Marc
