You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Marc Hoppins <ma...@eset.com> on 2021/11/26 11:48:56 UTC
Again: testing
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
Re: Again: testing
Posted by Mark Jens <ma...@gmail.com>.
On Tue, 7 Dec 2021 at 09:33, Marc Hoppins <ma...@eset.com> wrote:
> I have been following this guide:
>
>
>
>
> https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.6
>
>
>
> openJDK1.8
>
> Python 2.7
>
> Maven 3.6.3
>
>
>
> It is a fresh OS install (virtual machine) Ubuntu 20.04.
>
>
>
> Here are the console maven errors and ECLIPSE returned errors/messages.
>
>
>
> [INFO] Rat check: Summary over all files. Unapproved: 1, unknown: 1,
> generated: 0, approved: 1547 licenses.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.7.6.0.0 .............................. FAILURE [
> 2.580 s]
> [INFO] Apache Ambari Project POM 2.7.6.0.0 ................ SKIPPED
> [INFO] Ambari Web 2.7.6.0.0 ............................... SKIPPED
> [INFO] Ambari Views 2.7.6.0.0 ............................. SKIPPED
> [INFO] Ambari Admin View 2.7.6.0.0 ........................ SKIPPED
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT .................... SKIPPED
> [INFO] ambari-metrics 2.7.6.0.0 ........................... SKIPPED
> [INFO] Ambari Metrics Common 2.7.6.0.0 .................... SKIPPED
> [INFO] Ambari Metrics Hadoop Sink 2.7.6.0.0 ............... SKIPPED
> [INFO] Ambari Metrics Flume Sink 2.7.6.0.0 ................ SKIPPED
> [INFO] Ambari Metrics Kafka Sink 2.7.6.0.0 ................ SKIPPED
> [INFO] Ambari Metrics Storm Sink 2.7.6.0.0 ................ SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.6.0.0 ....... SKIPPED
> [INFO] Ambari Metrics Collector 2.7.6.0.0 ................. SKIPPED
> [INFO] Ambari Metrics Monitor 2.7.6.0.0 ................... SKIPPED
> [INFO] Ambari Metrics Grafana 2.7.6.0.0 ................... SKIPPED
> [INFO] Ambari Metrics Host Aggregator 2.7.6.0.0 ........... SKIPPED
> [INFO] Ambari Metrics Assembly 2.7.6.0.0 .................. SKIPPED
> [INFO] Ambari Service Advisor 1.0.0.0-SNAPSHOT ............ SKIPPED
> [INFO] Ambari Server 2.7.6.0.0 ............................ SKIPPED
> [INFO] Ambari Functional Tests 2.7.6.0.0 .................. SKIPPED
> [INFO] Ambari Agent 2.7.6.0.0 ............................. SKIPPED
> [INFO] ambari-logsearch 2.7.6.0.0 ......................... SKIPPED
> [INFO] Ambari Logsearch Appender 2.7.6.0.0 ................ SKIPPED
> [INFO] Ambari Logsearch Config Api 2.7.6.0.0 .............. SKIPPED
> [INFO] Ambari Logsearch Config JSON 2.7.6.0.0 ............. SKIPPED
> [INFO] Ambari Logsearch Config Solr 2.7.6.0.0 ............. SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper 2.7.6.0.0 ........ SKIPPED
> [INFO] Ambari Logsearch Config Local 2.7.6.0.0 ............ SKIPPED
> [INFO] Ambari Logsearch Log Feeder Plugin Api 2.7.6.0.0 ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder Container Registry 2.7.6.0.0 SKIPPED
> [INFO] Ambari Logsearch Log Feeder 2.7.6.0.0 .............. SKIPPED
> [INFO] Ambari Logsearch Web 2.7.6.0.0 ..................... SKIPPED
> [INFO] Ambari Logsearch Server 2.7.6.0.0 .................. SKIPPED
> [INFO] Ambari Logsearch Assembly 2.7.6.0.0 ................ SKIPPED
> [INFO] Ambari Logsearch Integration Test 2.7.6.0.0 ........ SKIPPED
> [INFO] ambari-infra 2.7.6.0.0 ............................. SKIPPED
> [INFO] Ambari Infra Solr Client 2.7.6.0.0 ................. SKIPPED
> [INFO] Ambari Infra Solr Plugin 2.7.6.0.0 ................. SKIPPED
> [INFO] Ambari Infra Manager 2.7.6.0.0 ..................... SKIPPED
> [INFO] Ambari Infra Assembly 2.7.6.0.0 .................... SKIPPED
> [INFO] Ambari Infra Manager Integration Tests 2.7.6.0.0 ... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2.864 s
> [INFO] Finished at: 2021-12-07T08:06:13+01:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check
> (default) on project ambari: Too many files with unapproved license: 1 See
> RAT report in: /home/march/Downloads/apache-ambari-2.7.6-src/target/rat.txt
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.rat:apache-rat-plugin:0.12:check (default) on project
> ambari: Too many files with unapproved license: 1 See RAT report in:
> /home/march/Downloads/apache-ambari-2.7.6-src/target/rat.txt
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.rat.mp.RatCheckException: Too many files with
> unapproved license: 1 See RAT report in:
> /home/march/Downloads/apache-ambari-2.7.6-src/target/rat.txt
> at org.apache.rat.mp.RatCheckMojo.check (RatCheckMojo.java:183)
> at org.apache.rat.mp.RatCheckMojo.execute (RatCheckMojo.java:156)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>
>
> RAT messages
>
> JavaDocs are generated, thus a license header is optional.
> Generated files do not require license headers.
>
> 1 Unknown Licenses
>
> *****************************************************
>
> Files with unapproved licenses:
>
> .jpb/persistence-units.xml
>
You should either:
1) remove this file
2) skip Rat (-Drat.skip)
3) add it to Rat whitelist
Then please paste the next error!
>
> *****************************************************
>
>
>
> *****************************************************
>
> Printing headers for text files without a valid license header...
>
> =====================================================
> == File: .jpb/persistence-units.xml
> =====================================================
> <?xml version="1.0" encoding="UTF-8"?>
> <project version="4">
> <component name="PersistenceUnitSettings">
> <persistence-units>
> <persistence-unit name="Default">
> <packages>
> <package value="org.apache.ambari.server.configuration.spring" />
> </packages>
> </persistence-unit>
> </persistence-units>
> </component>
> </project>
>
>
>
> Eclipse build messages
>
> Description Resource Path Location Type
> Invalid plugin configuration: version pom.xml /apache-ambari-2.7.6-src
> line 260 Language Servers
> Plugin could not be resolved. Ensure the plugin's groupId, artifactId and
> version are present.
>
> Additional information: Unable to resolve
> com.atlassian.maven.plugins:clover-maven-plugin pom.xml
> /apache-ambari-2.7.6-src line 564 Language Servers
> Plugin could not be resolved. Ensure the plugin's groupId, artifactId and
> version are present.
>
> Additional information: Unable to resolve
> org.apache.maven.plugins:maven-gpg-plugin pom.xml /apache-ambari-2.7.6-src
> line 654 Language Servers
> Plugin could not be resolved. Ensure the plugin's groupId, artifactId and
> version are present.
>
> Additional information: Unable to resolve
> org.apache.maven.plugins:maven-javadoc-plugin pom.xml
> /apache-ambari-2.7.6-src line 623 Language Servers
> Plugin could not be resolved. Ensure the plugin's groupId, artifactId and
> version are present.
>
> Additional information: Unable to resolve
> org.apache.maven.plugins:maven-source-plugin pom.xml
> /apache-ambari-2.7.6-src line 603 Language Servers
>
>
>
> *From:* Mark Jens <ma...@gmail.com>
> *Sent:* Monday, December 6, 2021 10:35 AM
> *To:* user@ambari.apache.org
> *Subject:* Re: Again: testing
>
>
>
> EXTERNAL
>
> Hi Marc,
>
>
>
> Which branch do you try to build ?
>
> Which versions of Java and Maven do you use ?
>
> Please paste the Maven error.
>
>
>
> On Mon, 6 Dec 2021 at 11:17, Marc Hoppins <ma...@eset.com> wrote:
>
> 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 <ma...@eset.com>
> *Sent:* Friday, November 26, 2021 12:49 PM
> *To:* user@ambari.apache.org
> *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
>
>
RE: Again: testing
Posted by Marc Hoppins <ma...@eset.com>.
I have been following this guide:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.6
openJDK1.8
Python 2.7
Maven 3.6.3
It is a fresh OS install (virtual machine) Ubuntu 20.04.
Here are the console maven errors and ECLIPSE returned errors/messages.
[INFO] Rat check: Summary over all files. Unapproved: 1, unknown: 1, generated: 0, approved: 1547 licenses.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main 2.7.6.0.0 .............................. FAILURE [ 2.580 s]
[INFO] Apache Ambari Project POM 2.7.6.0.0 ................ SKIPPED
[INFO] Ambari Web 2.7.6.0.0 ............................... SKIPPED
[INFO] Ambari Views 2.7.6.0.0 ............................. SKIPPED
[INFO] Ambari Admin View 2.7.6.0.0 ........................ SKIPPED
[INFO] ambari-utility 1.0.0.0-SNAPSHOT .................... SKIPPED
[INFO] ambari-metrics 2.7.6.0.0 ........................... SKIPPED
[INFO] Ambari Metrics Common 2.7.6.0.0 .................... SKIPPED
[INFO] Ambari Metrics Hadoop Sink 2.7.6.0.0 ............... SKIPPED
[INFO] Ambari Metrics Flume Sink 2.7.6.0.0 ................ SKIPPED
[INFO] Ambari Metrics Kafka Sink 2.7.6.0.0 ................ SKIPPED
[INFO] Ambari Metrics Storm Sink 2.7.6.0.0 ................ SKIPPED
[INFO] Ambari Metrics Storm Sink (Legacy) 2.7.6.0.0 ....... SKIPPED
[INFO] Ambari Metrics Collector 2.7.6.0.0 ................. SKIPPED
[INFO] Ambari Metrics Monitor 2.7.6.0.0 ................... SKIPPED
[INFO] Ambari Metrics Grafana 2.7.6.0.0 ................... SKIPPED
[INFO] Ambari Metrics Host Aggregator 2.7.6.0.0 ........... SKIPPED
[INFO] Ambari Metrics Assembly 2.7.6.0.0 .................. SKIPPED
[INFO] Ambari Service Advisor 1.0.0.0-SNAPSHOT ............ SKIPPED
[INFO] Ambari Server 2.7.6.0.0 ............................ SKIPPED
[INFO] Ambari Functional Tests 2.7.6.0.0 .................. SKIPPED
[INFO] Ambari Agent 2.7.6.0.0 ............................. SKIPPED
[INFO] ambari-logsearch 2.7.6.0.0 ......................... SKIPPED
[INFO] Ambari Logsearch Appender 2.7.6.0.0 ................ SKIPPED
[INFO] Ambari Logsearch Config Api 2.7.6.0.0 .............. SKIPPED
[INFO] Ambari Logsearch Config JSON 2.7.6.0.0 ............. SKIPPED
[INFO] Ambari Logsearch Config Solr 2.7.6.0.0 ............. SKIPPED
[INFO] Ambari Logsearch Config Zookeeper 2.7.6.0.0 ........ SKIPPED
[INFO] Ambari Logsearch Config Local 2.7.6.0.0 ............ SKIPPED
[INFO] Ambari Logsearch Log Feeder Plugin Api 2.7.6.0.0 ... SKIPPED
[INFO] Ambari Logsearch Log Feeder Container Registry 2.7.6.0.0 SKIPPED
[INFO] Ambari Logsearch Log Feeder 2.7.6.0.0 .............. SKIPPED
[INFO] Ambari Logsearch Web 2.7.6.0.0 ..................... SKIPPED
[INFO] Ambari Logsearch Server 2.7.6.0.0 .................. SKIPPED
[INFO] Ambari Logsearch Assembly 2.7.6.0.0 ................ SKIPPED
[INFO] Ambari Logsearch Integration Test 2.7.6.0.0 ........ SKIPPED
[INFO] ambari-infra 2.7.6.0.0 ............................. SKIPPED
[INFO] Ambari Infra Solr Client 2.7.6.0.0 ................. SKIPPED
[INFO] Ambari Infra Solr Plugin 2.7.6.0.0 ................. SKIPPED
[INFO] Ambari Infra Manager 2.7.6.0.0 ..................... SKIPPED
[INFO] Ambari Infra Assembly 2.7.6.0.0 .................... SKIPPED
[INFO] Ambari Infra Manager Integration Tests 2.7.6.0.0 ... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.864 s
[INFO] Finished at: 2021-12-07T08:06:13+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check (default) on project ambari: Too many files with unapproved license: 1 See RAT report in: /home/march/Downloads/apache-ambari-2.7.6-src/target/rat.txt -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check (default) on project ambari: Too many files with unapproved license: 1 See RAT report in: /home/march/Downloads/apache-ambari-2.7.6-src/target/rat.txt
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.rat.mp.RatCheckException: Too many files with unapproved license: 1 See RAT report in: /home/march/Downloads/apache-ambari-2.7.6-src/target/rat.txt
at org.apache.rat.mp.RatCheckMojo.check (RatCheckMojo.java:183)
at org.apache.rat.mp.RatCheckMojo.execute (RatCheckMojo.java:156)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
RAT messages
JavaDocs are generated, thus a license header is optional.
Generated files do not require license headers.
1 Unknown Licenses
*****************************************************
Files with unapproved licenses:
.jpb/persistence-units.xml
*****************************************************
*****************************************************
Printing headers for text files without a valid license header...
=====================================================
== File: .jpb/persistence-units.xml
=====================================================
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="PersistenceUnitSettings">
<persistence-units>
<persistence-unit name="Default">
<packages>
<package value="org.apache.ambari.server.configuration.spring" />
</packages>
</persistence-unit>
</persistence-units>
</component>
</project>
Eclipse build messages
Description Resource Path Location Type
Invalid plugin configuration: version pom.xml /apache-ambari-2.7.6-src line 260 Language Servers
Plugin could not be resolved. Ensure the plugin's groupId, artifactId and version are present.
Additional information: Unable to resolve com.atlassian.maven.plugins:clover-maven-plugin pom.xml /apache-ambari-2.7.6-src line 564 Language Servers
Plugin could not be resolved. Ensure the plugin's groupId, artifactId and version are present.
Additional information: Unable to resolve org.apache.maven.plugins:maven-gpg-plugin pom.xml /apache-ambari-2.7.6-src line 654 Language Servers
Plugin could not be resolved. Ensure the plugin's groupId, artifactId and version are present.
Additional information: Unable to resolve org.apache.maven.plugins:maven-javadoc-plugin pom.xml /apache-ambari-2.7.6-src line 623 Language Servers
Plugin could not be resolved. Ensure the plugin's groupId, artifactId and version are present.
Additional information: Unable to resolve org.apache.maven.plugins:maven-source-plugin pom.xml /apache-ambari-2.7.6-src line 603 Language Servers
From: Mark Jens <ma...@gmail.com>
Sent: Monday, December 6, 2021 10:35 AM
To: user@ambari.apache.org
Subject: Re: Again: testing
EXTERNAL
Hi Marc,
Which branch do you try to build ?
Which versions of Java and Maven do you use ?
Please paste the Maven error.
On Mon, 6 Dec 2021 at 11:17, Marc Hoppins <ma...@eset.com>> wrote:
Hi all,
Am still getting build failures in regard to atlassion clover/clover2 and apache.org<http://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 <ma...@eset.com>>
Sent: Friday, November 26, 2021 12:49 PM
To: user@ambari.apache.org<ma...@ambari.apache.org>
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
Re: Again: testing
Posted by Mark Jens <ma...@gmail.com>.
Hi Marc,
Which branch do you try to build ?
Which versions of Java and Maven do you use ?
Please paste the Maven error.
On Mon, 6 Dec 2021 at 11:17, Marc Hoppins <ma...@eset.com> wrote:
> 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 <ma...@eset.com>
> *Sent:* Friday, November 26, 2021 12:49 PM
> *To:* user@ambari.apache.org
> *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
>
RE: Again: testing
Posted by Marc Hoppins <ma...@eset.com>.
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 <ma...@eset.com>
Sent: Friday, November 26, 2021 12:49 PM
To: user@ambari.apache.org
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