Hi Bosco, Thanks for your reply!
Your script did resolve the pre-requisite package issue. Step 1: run your script [INFO] Ambari Main ........................................ FAILURE [ 0.521 s] [INFO] Apache Ambari Project POM .......................... SKIPPED [INFO] Ambari Web ......................................... SKIPPED Step 2: After running your script, then I ran "mvn clean install package -DskipTests" [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 41 licence. [INFO] [INFO] --- maven-assembly-plugin:2.2-beta-5:single (build-tarball) @ ambari-groovy-shell --- [INFO] Assemblies have been skipped per configuration of the skipAssembly parameter. [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ ambari-groovy-shell --- [INFO] Building jar: /edh_all_sources/edh_2.6.0/apache-ambari-2.2.2-src/ambari-shell/ambari-groovy-shell/target/ambari-groovy-shell-2.2.2.0.0.jar [INFO] [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ ambari-groovy-shell --- [INFO] Assemblies have been skipped per configuration of the skipAssembly parameter. [INFO] [INFO] --- spring-boot-maven-plugin:1.0.2.RELEASE:repackage (default) @ ambari-groovy-shell --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Ambari Main ........................................ SUCCESS [ 2.093 s] [INFO] Apache Ambari Project POM .......................... SUCCESS [ 0.070 s] [INFO] Ambari Web ......................................... SUCCESS [04:34 min] [INFO] Ambari Views ....................................... SUCCESS [ 1.108 s] [INFO] Ambari Admin View .................................. SUCCESS [05:33 min] [INFO] ambari-metrics ..................................... SUCCESS [ 0.455 s] [INFO] Ambari Metrics Common .............................. SUCCESS [ 1.205 s] [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [ 1.972 s] [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [ 1.061 s] [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [ 1.699 s] [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [ 2.077 s] [INFO] Ambari Metrics Collector ........................... SUCCESS [ 17.234 s] [INFO] Ambari Metrics Monitor ............................. SUCCESS [ 8.011 s] [INFO] Ambari Metrics Grafana ............................. SUCCESS [ 8.841 s] [INFO] Ambari Metrics Assembly ............................ SUCCESS [01:36 min] [INFO] Ambari Server ...................................... SUCCESS [02:40 min] [INFO] Ambari Agent ....................................... SUCCESS [ 1.988 s] [INFO] Ambari Client ...................................... SUCCESS [ 0.030 s] [INFO] Ambari Python Client ............................... SUCCESS [ 0.923 s] [INFO] Ambari Groovy Client ............................... SUCCESS [01:32 min] [INFO] Ambari Shell ....................................... SUCCESS [ 0.035 s] [INFO] Ambari Python Shell ................................ SUCCESS [ 0.361 s] [INFO] Ambari Groovy Shell ................................ SUCCESS [02:26 min] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 19:11 min [INFO] Finished at: 2016-07-28T23:46:04+08:00 [INFO] Final Memory: 358M/3392M [INFO] ------------------------------------------------------------------------ Its result looks good! Is "mvn clean install package -DskipTests" correct command to build Ambari? Regards On Thu, Jul 28, 2016 at 10:29 PM, Ascot Moss <[email protected]> wrote: > Hi, > > Thanks! > > > My current status as follows: > > *mvn clean && mvn -B -e clean install package rpm:rpm -Dbuild-rpm > -Dpython.ver='python >= 2.6' **-DskipTests* > > [INFO] RPM build errors: > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Reactor Summary: > > [INFO] > > [INFO] Ambari Main ........................................ SUCCESS [ > 3.747 s] > > [INFO] Apache Ambari Project POM .......................... SUCCESS [ > 0.345 s] > > [INFO] Ambari Web ......................................... SUCCESS [04:33 > min] > > [INFO] Ambari Views ....................................... SUCCESS [ > 1.672 s] > > [INFO] Ambari Admin View .................................. SUCCESS [ > 19.573 s] > > [INFO] ambari-metrics ..................................... SUCCESS [ > 1.075 s] > > [INFO] Ambari Metrics Common .............................. SUCCESS [ > 1.200 s] > > [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [ > 2.021 s] > > [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [ > 1.500 s] > > [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [ > 1.162 s] > > [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [ > 2.073 s] > > [INFO] Ambari Metrics Collector ........................... SUCCESS [01:48 > min] > > [INFO] Ambari Metrics Monitor ............................. SUCCESS [ > 1.588 s] > > [INFO] Ambari Metrics Grafana ............................. SUCCESS [ > 9.783 s] > > [INFO] Ambari Metrics Assembly ............................ SUCCESS [05:18 > min] > > [INFO] Ambari Server ...................................... SUCCESS [03:22 > min] > > [INFO] Ambari Agent ....................................... SUCCESS [ > 16.770 s] > > [INFO] Ambari Client ...................................... SUCCESS [ > 0.496 s] > > [INFO] Ambari Python Client ............................... FAILURE [ > 1.067 s] > > [INFO] Ambari Groovy Client ............................... SKIPPED > > [INFO] Ambari Shell ....................................... SKIPPED > > [INFO] Ambari Python Shell ................................ SKIPPED > > [INFO] Ambari Groovy Shell ................................ SKIPPED > > [INFO] > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Total time: 16:06 min > > [INFO] Finished at: 2016-07-28T22:23:55+08:00 > > [INFO] Final Memory: 335M/3132M > > [INFO] > ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal > org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project > python-client: RPM build execution returned: '1' executing '/bin/sh -c cd > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS > && rpmbuild -bb --buildroot > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot > --define '_topdir > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' > --target x86_64-redhat-linux python-client.spec' -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on > project python-client: RPM build execution returned: '1' executing '/bin/sh > -c cd > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS > && rpmbuild -bb --buildroot > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot > --define '_topdir > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' > --target x86_64-redhat-linux python-client.spec' > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > > 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:497) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > > Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build > execution returned: '1' executing '/bin/sh -c cd > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS > && rpmbuild -bb --buildroot > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot > --define '_topdir > /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' > --target x86_64-redhat-linux python-client.spec' > > at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150) > > at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792) > > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > > ... 20 more > > [ERROR] > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [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/MojoExecutionException > > [ERROR] > > [ERROR] After correcting the problems, you can resume the build with the > command > > [ERROR] mvn <goals> -rf :python-client > > > > > On Thu, Jul 28, 2016 at 8:42 PM, Don Bosco Durai <[email protected]> wrote: > >> Ascot >> >> >> >> Would you be able to use Dockers to build Ambari? I have uploaded a >> script to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944 >> >> >> >> If you are using CentOS, then you would have to install Dockers. And then >> copy the script from the JIRA to the root folder of your Ambari source. You >> might need to chmod a+x to the script. >> >> >> >> When the first time you run the script, it will create the build the >> image and run it. Next time onwards, it will just run it. >> >> >> >> Give a try and let me know if it works for you. >> >> >> >> Thanks >> >> >> >> Bosco >> >> >> >> >> >> *From: *Ascot Moss <[email protected]> >> *Reply-To: *<[email protected]> >> *Date: *Thursday, July 28, 2016 at 3:29 AM >> >> *To: *<[email protected]> >> *Subject: *Re: Build Error >> >> >> >> *Hi,* >> >> >> >> *Thanks for your reply!!* >> >> *Just tried ur command, can get thru *[INFO] Ambari Web >> ......................................... SUCCESS [04:52 min] >> >> >> >> *Looks like " -Dstack.distribution" must be specified.Moving on >> *ambari-metrics >> now. >> >> Regards >> >> >> >> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >> >= 2.6' -Dstack.distribution=HDP* >> >> [INFO] Ambari Main ........................................ SUCCESS [ >> 7.205 s] >> >> [INFO] Apache Ambari Project POM .......................... SUCCESS [ >> 0.297 s] >> >> [INFO] Ambari Web ......................................... SUCCESS >> [04:52 min] >> >> [INFO] Ambari Views ....................................... SUCCESS [ >> 2.297 s] >> >> [INFO] Ambari Admin View .................................. SUCCESS [ >> 19.035 s] >> >> [INFO] ambari-metrics ..................................... FAILURE [ >> 0.174 s] >> >> >> >> On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <[email protected]> >> wrote: >> >> This is what I run on my machine: >> >> >> >> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >> >= 2.6' -Dstack.distribution=HDP >> >> >> >> Your error seems to be something related to npm since I see an error on >> lstat package.json >> >> >> >> May be try cleaning the npm cache under ambari-web: >> >> Go to ambari-src-folder/ambari-web and run the command npm cache clean >> >> Go back to ambari-src-folder and run the build command again? >> >> >> >> On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <[email protected]> >> wrote: >> >> Found error in log >> >> 50462 silly gunzTarPerm extractEntry .npmignore >> >> 50463 silly gunzTarPerm extractEntry index.js >> >> 50464 silly gunzTarPerm extractEntry .npmignore >> >> 50465 silly gunzTarPerm extractEntry index.js >> >> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 [email protected] >> >> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 [email protected] >> >> 50468 verbose about to build >> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect >> >> 50469 >> info >> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect >> unbuild >> >> 50470 info preuninstall [email protected] >> >> 50471 error Error: ENOENT, lstat >> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json' >> >> 50472 error If you need help, you may report this log at: >> >> 50472 error <http://github.com/isaacs/npm/issues> >> >> 50472 error or email it to: >> >> 50472 error <[email protected]> >> >> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64 >> >> 50474 error command "node" "/usr/bin/npm" "install" >> >> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web >> >> 50476 error node -v v0.10.42 >> >> 50477 error npm -v 1.3.6 >> >> 50478 error path >> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json >> >> 50479 error fstream_path >> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json >> >> 50480 error fstream_type File >> >> 50481 error fstream_class FileWriter >> >> 50482 error code ENOENT >> >> 50483 error errno 34 >> >> 50484 error fstream_stack >> /usr/lib/node_modules/fstream/lib/writer.js:284:26 >> >> 50484 error fstream_stack Object.oncomplete (fs.js:108:15) >> >> 50485 verbose exit [ 34, true ] >> >> >> >> >> >> >> >> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <[email protected]> >> wrote: >> >> By the way, below are my steps: >> >> Please let me know if correct or not, many thanks! >> >> --------------- >> >> tar xfvz apache-ambari-2.2.2-src.tar.gz >> >> cd apache-ambari-2.2.2-src >> >> *mvn clean * >> >> *pushd ambari-metrics * >> >> *mvn versions:set -DnewVersion=2.2.2.1 * >> >> *popd * >> >> *mvn versions:set -DnewVersion=2.2.2.1 * >> >> >> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests >> -Dpython.ver="python >= 2.6" -Preplaceurl -e*--------------- >> >> >> >> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <[email protected]> >> wrote: >> >> My OS is CentOS 7: >> >> >> $node --version >> >> v6.3.0 >> >> >> >> $ npm --version >> >> 3.10.5 >> >> >> >> $ brunch --version >> >> 2.8.2 >> >> >> >> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <[email protected]> >> wrote: >> >> I would assume mvn to install the required version of node, npm and >> brunch. >> >> >> >> This is what I have on my environment (which does mvn builds without any >> issues): >> >> bash-3.2$ node --version >> >> v0.10.39 >> >> bash-3.2$ npm --version >> >> 1.4.28 >> >> bash-3.2$ brunch --version >> >> 1.8.5 >> >> >> >> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <[email protected]> wrote: >> >> >> Hi, >> >> >> >> Thanks for your reply! >> >> >> >> Tried the following: >> >> (step 1) >> npm install -g brunch >> >> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch >> >> /usr/lib >> >> └─┬ [email protected] >> >> ├─┬ [email protected] >> >> │ └─┬ [email protected] >> >> │ └── [email protected] >> >> └─┬ [email protected] >> >> └─┬ [email protected] >> >> └── [email protected] >> npm WARN optional Skipping failed optional dependency >> /brunch/chokidar/fsevents: >> npm WARN notsup Not compatible with your operating system or >> architecture: [email protected] >> >> >> >> (step 2) >> >> tar xfvz apache-ambari-2.2.2-src.tar.gz >> >> cd apache-ambari-2.2.2-src >> >> *mvn clean* >> >> *mvn versions:set -DnewVersion=2.2.2.1* >> >> *pushd ambari-metrics* >> >> *mvn versions:set -DnewVersion=2.2.2.1* >> >> *popd* >> >> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests >> -Dpython.ver="python >= 2.6" -Preplaceurl -e* >> >> >> >> [ERROR] Failed to execute goal >> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project >> ambari-web: Command execution failed. Process exited with an error: 1 (Exit >> value: 1) -> [Help 1] >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on >> project ambari-web: Command execution failed. >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) >> >> at >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) >> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) >> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) >> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) >> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) >> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) >> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) >> >> 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:497) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) >> >> Caused by: org.apache.maven.plugin.MojoExecutionException: Command >> execution failed. >> >> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362) >> >> at >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) >> >> ... 20 more >> >> Caused by: org.apache.commons.exec.ExecuteException: Process exited with >> an error: 1 (Exit value: 1) >> >> at >> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377) >> >> at >> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160) >> >> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610) >> >> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352) >> >> ... 22 more >> >> [ERROR] >> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> >> [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/MojoExecutionException >> >> [ERROR] >> >> [ERROR] After correcting the problems, you can resume the build with the >> command >> >> [ERROR] mvn <goals> -rf :ambari-web >> >> >> >> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <[email protected]> >> wrote: >> >> See if *npm install -g brunch* would fix the issue? >> >> >> >> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <[email protected]> wrote: >> >> Hi >> thanks for your reply! >> >> Added -e >> >> >> >> >> >> npm WARN optional Skipping failed optional dependency /chokidar/fsevents: >> >> npm WARN notsup Not compatible with your operating system or >> architecture: [email protected] >> >> npm WARN [email protected] No license field. >> >> [INFO] >> >> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web --- >> >> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: >> perhaps you meant defaultExtensions >> >> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps >> you meant defaultExtensions >> >> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant >> order >> >> 28 Jul 07:46:20 - error: Initialization error - You probably need to >> execute `npm install` to install brunch plugins. SyntaxError: Setter must >> have exactly one formal parameter. >> >> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace. >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] Reactor Summary: >> >> [INFO] >> >> [INFO] Ambari Main ........................................ SUCCESS [ >> 6.635 s] >> >> [INFO] Apache Ambari Project POM .......................... SUCCESS [ >> 0.371 s] >> >> [INFO] Ambari Web ......................................... FAILURE >> [02:46 min] >> >> [INFO] Ambari Views ....................................... SKIPPED >> >> [INFO] Ambari Admin View .................................. SKIPPED >> >> [INFO] ambari-metrics ..................................... SKIPPED >> >> [INFO] Ambari Metrics Common .............................. SKIPPED >> >> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED >> >> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED >> >> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED >> >> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED >> >> [INFO] Ambari Metrics Collector ........................... SKIPPED >> >> [INFO] Ambari Metrics Monitor ............................. SKIPPED >> >> [INFO] Ambari Metrics Grafana ............................. SKIPPED >> >> [INFO] Ambari Metrics Assembly ............................ SKIPPED >> >> [INFO] Ambari Server ...................................... SKIPPED >> >> [INFO] Ambari Agent ....................................... SKIPPED >> >> [INFO] Ambari Client ...................................... SKIPPED >> >> [INFO] Ambari Python Client ............................... SKIPPED >> >> [INFO] Ambari Groovy Client ............................... SKIPPED >> >> [INFO] Ambari Shell ....................................... SKIPPED >> >> [INFO] Ambari Python Shell ................................ SKIPPED >> >> [INFO] Ambari Groovy Shell ................................ SKIPPED >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] BUILD FAILURE >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] Total time: 02:53 min >> >> [INFO] Finished at: 2016-07-28T07:46:20+08:00 >> >> [INFO] Final Memory: 33M/1036M >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [ERROR] Failed to execute goal >> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project >> ambari-web: Command execution failed. Process exited with an error: 1 (Exit >> value: 1) -> [Help 1] >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on >> project ambari-web: Command execution failed. >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) >> >> at >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) >> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) >> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) >> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) >> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) >> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) >> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) >> >> 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:497) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) >> >> Caused by: org.apache.maven.plugin.MojoExecutionException: Command >> execution failed. >> >> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362) >> >> at >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) >> >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) >> >> ... 20 more >> >> Caused by: org.apache.commons.exec.ExecuteException: Process exited with >> an error: 1 (Exit value: 1) >> >> at >> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377) >> >> at >> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160) >> >> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610) >> >> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352) >> >> ... 22 more >> >> >> >> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <[email protected]> >> wrote: >> >> Hi there- >> >> >> >> Adding -e to the mvn command will give you more output on your error. >> >> >> >> Thanks. >> >> >> >> Amanda >> >> >> >> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <[email protected]> >> wrote: >> >> as root (also tried as ordinary user) >> >> >> >> Refer to the error below, is it about some default settings must be >> adjusted in pom? >> >> [ERROR] Failed to execute goal >> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project >> ambari-web: Command execution failed. Process exited with an error: 1 (Exit >> value: 1) -> [Help 1] >> >> >> >> >> >> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <[email protected]> >> wrote: >> >> As which user are you running this build? I was having issues when I ran >> the build as user “root”. >> >> >> >> Thanks >> >> >> >> Bosco >> >> >> >> >> >> *From: *Ascot Moss <[email protected]> >> *Reply-To: *<[email protected]> >> *Date: *Tuesday, July 26, 2016 at 6:07 AM >> *To: *<[email protected]> >> *Subject: *Re: Build Error >> >> >> >> my mvn is 3.3.9, will this be an issue? >> >> >> >> >> >> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <[email protected]> wrote: >> >> Hi, >> >> >> >> >> >> Please help! >> >> I am trying to build Ambari 2.2.2, got the following error as follows: >> >> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace. >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] Reactor Summary: >> >> [INFO] >> >> [INFO] Ambari Main ........................................ SUCCESS >> [04:51 min] >> >> [INFO] Apache Ambari Project POM .......................... SUCCESS [ >> 4.361 s] >> >> [INFO] Ambari Web ......................................... FAILURE >> [02:55 min] >> >> [INFO] Ambari Views ....................................... SKIPPED >> >> [INFO] Ambari Admin View .................................. SKIPPED >> >> [INFO] ambari-metrics ..................................... SKIPPED >> >> [INFO] Ambari Metrics Common .............................. SKIPPED >> >> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED >> >> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED >> >> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED >> >> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED >> >> [INFO] Ambari Metrics Collector ........................... SKIPPED >> >> [INFO] Ambari Metrics Monitor ............................. SKIPPED >> >> [INFO] Ambari Metrics Grafana ............................. SKIPPED >> >> [INFO] Ambari Metrics Assembly ............................ SKIPPED >> >> [INFO] Ambari Server ...................................... SKIPPED >> >> [INFO] Ambari Agent ....................................... SKIPPED >> >> [INFO] Ambari Client ...................................... SKIPPED >> >> [INFO] Ambari Python Client ............................... SKIPPED >> >> [INFO] Ambari Groovy Client ............................... SKIPPED >> >> [INFO] Ambari Shell ....................................... SKIPPED >> >> [INFO] Ambari Python Shell ................................ SKIPPED >> >> [INFO] Ambari Groovy Shell ................................ SKIPPED >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] BUILD FAILURE >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [ERROR] Failed to execute goal >> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project >> ambari-web: Command execution failed. Process exited with an error: 1 (Exit >> value: 1) -> [Help 1] >> >> [ERROR] >> >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> >> [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/MojoExecutionException >> >> [ERROR] >> >> [ERROR] After correcting the problems, you can resume the build with the >> command >> >> [ERROR] mvn <goals> -rf :ambari-web >> >> >> >> Any ideas how to resolve it? >> >> Regards >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Thanks, >> >> >> >> Amanda Moran >> >> >> >> >> >> >> >> -- >> >> *Mithun Mathew* (Matt) >> >> - www.linkedin.com/in/mithunmatt/ >> >> >> >> >> >> >> >> -- >> >> *Mithun Mathew* (Matt) >> >> - www.linkedin.com/in/mithunmatt/ >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> *Mithun Mathew* (Matt) >> >> - www.linkedin.com/in/mithunmatt/ >> >> >> > >
