maven install fail - maven

I follow the guide of how to use PlayN with Maven, but when i perform the command:
maven install
it fails.
The error log is the following:
[INFO]
[INFO] --- maven-android-plugin:3.0.0-alpha-2:dex (default-dex) # playn-showcase-android ---
[INFO] /usr/lib/jvm/java-6-openjdk/jre/bin/java [-Xmx1024m, -jar, /opt/android-sdk/platform-tools/lib/dx.jar, --dex, --output=/home/hox/Projects/playn/playn/sample/showcase/android/target/classes.dex, /home/hox/Projects/playn/playn/sample/showcase/android/target/android-classes]
[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) # playn-showcase-android ---
[INFO] Building jar: /home/hox/Projects/playn/playn/sample/showcase/android/target/playn-showcase-android-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-android-plugin:3.0.0-alpha-2:apk (default-apk) # playn-showcase-android ---
[INFO] /opt/android-sdk/platform-tools/aapt [package, -f, -M, /home/hox/Projects/playn/playn/sample/showcase/android/AndroidManifest.xml, -S, /home/hox/Projects/playn/playn/sample/showcase/android/res, --auto-add-overlay, -I, /opt/android-sdk/platforms/android-11/android.jar, -F, /home/hox/Projects/playn/playn/sample/showcase/android/target/playn-showcase-android-1.0-SNAPSHOT.ap_]
[ERROR] Cannot create the APKBuilder object
java.lang.NullPointerException
at com.jayway.maven.plugins.android.phase09package.ApkBuilder.(ApkBuilder.java:195)
at com.jayway.maven.plugins.android.phase09package.ApkMojo.doAPKWithAPKBuilder(ApkMojo.java:334)
at com.jayway.maven.plugins.android.phase09package.ApkMojo.createApkFile(ApkMojo.java:249)
at com.jayway.maven.plugins.android.phase09package.ApkMojo.execute(ApkMojo.java:207)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] PlayN Project ..................................... SUCCESS [0.125s]
[INFO] PlayN Project Archetype ........................... SUCCESS [0.650s]
[INFO] PlayN Core ........................................ SUCCESS [1.962s]
[INFO] PlayN JBox2D ...................................... SUCCESS [2.125s]
[INFO] PlayN WebGL ....................................... SUCCESS [0.914s]
[INFO] PlayN Java ........................................ SUCCESS [1.740s]
[INFO] PlayN HTML ........................................ SUCCESS [1.419s]
[INFO] PlayN Flash ....................................... SUCCESS [1.414s]
[INFO] PlayN Android ..................................... SUCCESS [1.552s]
[INFO] PlayN Server ...................................... SUCCESS [0.524s]
[INFO] PlayN Demos Project ............................... SUCCESS [0.002s]
[INFO] PlayN Hello Metaproject ........................... SUCCESS [0.003s]
[INFO] PlayN Hello Core .................................. SUCCESS [0.574s]
[INFO] PlayN Hello HTML .................................. SUCCESS [18.829s]
[INFO] PlayN Hello Flash ................................. SUCCESS [22.045s]
[INFO] PlayN Hello Android ............................... SUCCESS [14.519s]
[INFO] PlayN Showcase Metaproject ........................ SUCCESS [0.003s]
[INFO] PlayN Showcase Core ............................... SUCCESS [1.567s]
[INFO] PlayN Showcase HTML ............................... SUCCESS [21.663s]
[INFO] PlayN Showcase Flash .............................. SUCCESS [35.783s]
[INFO] PlayN Showcase Android ............................ FAILURE [11.533s]
[INFO] PlayN Cute Metaproject ............................ SKIPPED
[INFO] PlayN Cute Core ................................... SKIPPED
[INFO] PlayN Cute HTML ................................... SKIPPED
[INFO] PlayN Cute Flash .................................. SKIPPED
[INFO] PlayN Cute Android ................................ SKIPPED
[INFO] PlayN Payments .................................... SKIPPED
[INFO] PlayN Payments Core ............................... SKIPPED
[INFO] PlayN Payments Demo Metaproject ................... SKIPPED
[INFO] PlayN Payments Demo Core .......................... SKIPPED
[INFO] PlayN payments HTML ............................... SKIPPED
[INFO] PlayN payments Server ............................. SKIPPED
[INFO] PlayN Payments Demo HTML .......................... SKIPPED
[INFO] PlayN Tests Metaproject ........................... SKIPPED
[INFO] PlayN Benchmark Metaproject ....................... SKIPPED
[INFO] PlayN Benchmarks Core ............................. SKIPPED
[INFO] PlayN Benchmark HTML .............................. SKIPPED
[INFO] PlayN Manual Tests Metaproject .................... SKIPPED
[INFO] PlayN Manual Tests Core ........................... SKIPPED
[INFO] PlayN Manual Tests HTML ........................... SKIPPED
[INFO] PlayN Manual Tests Flash .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:20.302s
[INFO] Finished at: Tue Oct 25 15:44:44 CEST 2011
[INFO] Final Memory: 122M/318M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.jayway.maven.plugins.android.generation2:maven-android-plugin:3.0.0-alpha-2:apk (default-apk) on project playn-showcase-android: Cannot create the APKBuilder object: NullPointerException -> [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 -rf :playn-showcase-android
I found the same error here, but no solution.

Are you using the recently released r14 of the Android SDK? It seems like it has some issues with the version of the Maven Android plugin playn uses. Try replacing the plugins section in samples/showcase/android/pom.xml with the following:
<plugins>
<plugin>
<groupId>com.jayway.maven.plugins.android.generation2</groupId>
<artifactId>android-maven-plugin</artifactId>
<version>3.0.0</version>
<configuration>
<androidManifestFile>${project.basedir}/AndroidManifest.xml</androidManifestFile>
<assetsDirectory>${project.basedir}/assets</assetsDirectory>
<resourceDirectory>${project.basedir}/res</resourceDirectory>
<sdk>
<platform>11</platform>
</sdk>
<undeployBeforeDeploy>true</undeployBeforeDeploy>
<jvmArguments>
<jvmArgument>-Xmx1024m</jvmArgument>
</jvmArguments>
<dex>
<jvmArguments>
<jvmArgument>-Xmx1024m</jvmArgument>
</jvmArguments>
</dex>
</configuration>
<extensions>true</extensions>
</plugin>
</plugins>
Then cd into samples/showcase and run mvn clean then mvn install.
If that works, I'll look at upgrading all the samples to use the latest android maven plugin later today.

Related

mvn sonar:sonar overrides the top level pom build time and runs sequentially at the end

After integrating sonar qube into my maven multi-module build and running
mvn -U -B -Dmaven.test.failure.ignore -Psonar verify sonar:sonar
I see the following build times
[2023-01-06T17:00:17.831Z] [INFO] ------------------------------------------------------------------------
[2023-01-06T17:00:17.831Z] [INFO] Reactor Summary for my-project 1.0.1:
[2023-01-06T17:00:17.831Z] [INFO]
[2023-01-06T17:00:17.831Z] [INFO] my-project ............................................ SUCCESS [01:52 min]
[2023-01-06T17:00:17.831Z] [INFO] my-project-common ..................................... SUCCESS [ 22.046 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-migration .................................. SUCCESS [ 3.998 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-test-common ................................ SUCCESS [ 33.710 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-dto ........................................ SUCCESS [ 3.010 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-producer ................................... SUCCESS [ 31.773 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-db ......................................... SUCCESS [01:07 min]
[2023-01-06T17:00:17.831Z] [INFO] my-project-utils ...................................... SUCCESS [ 23.637 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-server ..................................... SUCCESS [05:50 min]
[2023-01-06T17:00:17.831Z] [INFO] my-project-client ..................................... SUCCESS [ 32.758 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-http-client ................................ SUCCESS [ 5.322 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-integration ................................ SUCCESS [02:43 min]
[2023-01-06T17:00:17.831Z] [INFO] jacoco-coverage-report ................................ SUCCESS [ 8.389 s]
[2023-01-06T17:00:17.831Z] [INFO] my-project-other ...................................... SUCCESS [01:00 min]
[2023-01-06T17:00:17.831Z] [INFO] ------------------------------------------------------------------------
[2023-01-06T17:00:17.831Z] [INFO] BUILD SUCCESS
[2023-01-06T17:00:17.831Z] [INFO] ------------------------------------------------------------------------
[2023-01-06T17:00:17.831Z] [INFO] Total time: 15:22 min
[2023-01-06T17:00:17.831Z] [INFO] Finished at: 2023-01-06T17:00:17Z
[2023-01-06T17:00:17.831Z] [INFO] ------------------------------------------------------------------------
where the my-project .... build time of ~2 minutes took me by surprise.
Then on the console output I noticed the following
Building my-project 1.0.1 [15/14]
i.e. It builds the 15th step out of 14.
Examining the output it seems this is an extra step added by sonar. But it re-uses the the top level pom.xml name masking it's build time and hiding its own.
Is this expected? Is there a workaround to avoid the override?
I'm also curious if there is a way to integrate sonar and run its analysis in parallel rather than sequentially at the end?
i.e. It could analyse the finished modules while the next module is being built in parallel.
Note: The integration is via jacoco
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.8.5</version>
</plugin>

Cannot build Storm - Could not resolve dependencies for project org.apache.storm:storm-autocreds:jar:2.3.0

I have a problem with building a raw project wchi I got from Storm website.
I've cloned that repo: https://github.com/apache/storm/tree/v2.3.0/examples/storm-starter
and went with the instruction step by step. But it seems I have a problem with dependencies:
Can anybody try to build that repo? I'm using maven 3.x
I don't know if some dependencies changed theirs addres in repositories, or maybe I have something misconfigured.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Storm 2.3.0:
[INFO]
[INFO] Storm .............................................. FAILURE [ 10.277 s]
[INFO] Apache Storm - Checkstyle .......................... SKIPPED
[INFO] Shaded Deps for Storm Client ....................... SKIPPED
[INFO] multilang-javascript ............................... SKIPPED
[INFO] multilang-python ................................... SKIPPED
[INFO] multilang-ruby ..................................... SKIPPED
[INFO] maven-shade-clojure-transformer .................... SKIPPED
[INFO] storm-maven-plugins ................................ SKIPPED
[INFO] Storm Client ....................................... SKIPPED
[INFO] storm-server ....................................... SKIPPED
[INFO] storm-clojure ...................................... SKIPPED
[INFO] Storm Core ......................................... SKIPPED
[INFO] Storm Webapp ....................................... SKIPPED
[INFO] storm-clojure-test ................................. SKIPPED
[INFO] storm-submit-tools ................................. SKIPPED
[INFO] storm-autocreds .................................... SKIPPED
[INFO] storm-hdfs ......................................... SKIPPED
[INFO] storm-hdfs-blobstore ............................... SKIPPED
[INFO] storm-hdfs-oci ..................................... SKIPPED
[INFO] storm-hbase ........................................ SKIPPED
[INFO] storm-hive ......................................... SKIPPED
[INFO] storm-jdbc ......................................... SKIPPED
[INFO] storm-redis ........................................ SKIPPED
[INFO] storm-eventhubs .................................... SKIPPED
[INFO] storm-elasticsearch ................................ SKIPPED
[INFO] storm-solr ......................................... SKIPPED
[INFO] storm-metrics ...................................... SKIPPED
[INFO] storm-cassandra .................................... SKIPPED
[INFO] storm-mqtt ......................................... SKIPPED
[INFO] storm-mongodb ...................................... SKIPPED
[INFO] storm-kafka-client ................................. SKIPPED
[INFO] storm-kafka-migration .............................. SKIPPED
[INFO] storm-opentsdb ..................................... SKIPPED
[INFO] storm-kafka-monitor ................................ SKIPPED
[INFO] storm-kinesis ...................................... SKIPPED
[INFO] storm-jms .......................................... SKIPPED
[INFO] storm-pmml ......................................... SKIPPED
[INFO] storm-rocketmq ..................................... SKIPPED
[INFO] blobstore-migrator ................................. SKIPPED
[INFO] Storm Integration Test ............................. SKIPPED
[INFO] flux ............................................... SKIPPED
[INFO] flux-wrappers ...................................... SKIPPED
[INFO] flux-core .......................................... SKIPPED
[INFO] flux-examples ...................................... SKIPPED
[INFO] storm-sql-runtime .................................. SKIPPED
[INFO] storm-sql-core ..................................... SKIPPED
[INFO] storm-sql-kafka .................................... SKIPPED
[INFO] storm-sql-redis .................................... SKIPPED
[INFO] storm-sql-mongodb .................................. SKIPPED
[INFO] storm-sql-hdfs ..................................... SKIPPED
[INFO] sql ................................................ SKIPPED
[INFO] storm-starter ...................................... SKIPPED
[INFO] storm-loadgen ...................................... SKIPPED
[INFO] storm-mongodb-examples ............................. SKIPPED
[INFO] storm-redis-examples ............................... SKIPPED
[INFO] storm-opentsdb-examples ............................ SKIPPED
[INFO] storm-solr-examples ................................ SKIPPED
[INFO] storm-kafka-client-examples ........................ SKIPPED
[INFO] storm-jdbc-examples ................................ SKIPPED
[INFO] storm-hdfs-examples ................................ SKIPPED
[INFO] storm-hive-examples ................................ SKIPPED
[INFO] storm-elasticsearch-examples ....................... SKIPPED
[INFO] storm-mqtt-examples ................................ SKIPPED
[INFO] storm-pmml-examples ................................ SKIPPED
[INFO] storm-jms-examples ................................. SKIPPED
[INFO] storm-rocketmq-examples ............................ SKIPPED
[INFO] Storm Perf ......................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13.129 s
[INFO] Finished at: 2022-03-03T12:44:23+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project storm-autocreds: Could not resolve dependencies for project org.apache.storm:storm-autocreds:jar:2.3.0: Could not transfer artifact javax.jms:jms:jar:1.1 from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [datanucleus (http://www.datanucleus.org/downloads/maven2, default, releases), glassfish-repository (http://maven.glassfish.org/content/groups/glassfish, default, disabled), glassfish-repo-archive (http://maven.glassfish.org/content/groups/glassfish, default, disabled), apache.snapshots (http://repository.apache.org/snapshots, default, snapshots)] -> [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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :storm-autocreds

Hawkular server setup using maven give me error during build

Hawkular server setup using maven give me error during build. I am getting below error after run below command :
mvn clean install -Pdev -DskipTests -e
I am using git hub souce code to build this using link : https://github.com/hawkular/hawkular-apm/tree/master
[WARNING] npm WARN deprecated babel#6.5.2: Babel's CLI commands have been moved from the babel package to the babel-cli package
[WARNING] npm WARN deprecated vinyl-map#1.0.1: Missing dependencies resolved in v1.0.2 (Run 'npm update --save vinyl-map' to update package.json)
[WARNING] npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[WARNING] npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[WARNING] npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[WARNING] npm WARN deprecated minimatch#0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[WARNING] npm WARN deprecated node-uuid#1.4.7: use uuid module instead
[WARNING] npm WARN deprecated graceful-fs#2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Hawkular APM ....................................... SUCCESS [ 11.622 s]
[INFO] Hawkular APM::Client::Instrumentation JVM .......... SUCCESS [ 2.024 s]
[INFO] Hawkular APM::API .................................. SUCCESS [ 12.477 s]
[INFO] Hawkular APM::Client::API .......................... SUCCESS [ 1.301 s]
[INFO] Hawkular APM::Server::API .......................... SUCCESS [ 4.397 s]
[INFO] Hawkular APM::Tests::Parent ........................ SUCCESS [ 0.743 s]
[INFO] Hawkular APM::Tests::Common ........................ SUCCESS [ 0.942 s]
[INFO] Hawkular APM::Client::Collector .................... SUCCESS [ 1.769 s]
[INFO] Hawkular APM::Client::Trace Publisher REST Client .. SUCCESS [ 0.600 s]
[INFO] Hawkular APM::Client::Instrumenter ................. SUCCESS [ 3.242 s]
[INFO] Hawkular APM::Client::Config Service REST Client ... SUCCESS [ 0.672 s]
[INFO] Hawkular APM::Client::Agent ........................ SUCCESS [ 11.770 s]
[INFO] Hawkular APM::Client::OpenTracing .................. SUCCESS [ 2.608 s]
[INFO] Hawkular APM::Client::OpenTracing Agent ............ SUCCESS [ 2.005 s]
[INFO] Hawkular APM::Client::Analytics Service REST Client SUCCESS [ 0.599 s]
[INFO] Hawkular APM::Client::Kafka ........................ SUCCESS [ 0.877 s]
[INFO] Hawkular APM::Client::Trace Service REST Client .... SUCCESS [ 0.556 s]
[INFO] Hawkular APM::Examples::Vertx Opentracing .......... SUCCESS [ 0.550 s]
[INFO] Hawkular APM::Examples::Vertx Opentracing::Common .. SUCCESS [ 1.142 s]
[INFO] Hawkular APM::Examples::Vertx Opentracing::Account Manager SUCCESS [ 3.121 s]
[INFO] Hawkular APM::Examples::Vertx Opentracing::Inventory Manager SUCCESS [ 2.613 s]
[INFO] Hawkular APM::Examples::Vertx Opentracing::Order Log SUCCESS [ 2.547 s]
[INFO] Hawkular APM::Examples::Vertx Opentracing::Order Manager SUCCESS [ 2.939 s]
[INFO] Hawkular APM::Server::Elasticsearch ................ SUCCESS [ 4.698 s]
[INFO] Hawkular APM::Server::Infinispan ................... SUCCESS [ 1.564 s]
[INFO] Hawkular APM::Server::Processors ................... SUCCESS [ 1.926 s]
[INFO] Hawkular APM::Server::Processors::Zipkin ........... SUCCESS [ 1.488 s]
[INFO] Hawkular APM::Server::JMS .......................... SUCCESS [ 2.246 s]
[INFO] Hawkular APM::Server::Kafka ........................ SUCCESS [ 1.072 s]
[INFO] Hawkular APM::Server::Processors::Alerts Publisher . SUCCESS [ 1.325 s]
[INFO] Hawkular APM::Server::REST ......................... SUCCESS [ 2.697 s]
[INFO] Hawkular APM::Server::Security Provider::JAAS ...... SUCCESS [ 0.566 s]
[INFO] Hawkular APM::Server::Zipkin REST .................. SUCCESS [ 0.690 s]
[INFO] Hawkular APM::Server::Zipkin WAR ................... SUCCESS [ 2.372 s]
[INFO] Hawkular APM::Server::WAR .......................... SUCCESS [ 2.235 s]
[INFO] Hawkular APM::UI::Console .......................... FAILURE [ 28.713 s]
[INFO] Hawkular APM::Distribution ......................... SKIPPED
[INFO] Hawkular APM::Tests::App::Swarm polyglot OpenTracing SKIPPED
[INFO] Hawkular APM::Tests::OpenTracing Agent ............. SKIPPED
[INFO] Hawkular APM::Tests::Containers::Jetty ............. SKIPPED
[INFO] Hawkular APM::Tests::Containers::Standalone ........ SKIPPED
[INFO] Hawkular APM::Tests::Containers::Wildfly ........... SKIPPED
[INFO] Hawkular APM::Tests::Instrumentation ............... SKIPPED
[INFO] Hawkular APM::Tests::Instrumentation Test Framework SKIPPED
[INFO] Hawkular APM::Tests::Distribution .................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:05 min
[INFO] Finished at: 2017-01-18T03:45:12-05:00
[INFO] Final Memory: 127M/239M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project hawkular-apm-ui: Failed to run task: 'npm install' failed. (error code 137) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project hawkular-apm-ui: Failed to run task
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.MojoFailureException: Failed to run task
at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:95)
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: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'npm install' failed. (error code 137)
at com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:60)
at com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:62)
at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:89)
... 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/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :hawkular-apm-ui
Thanks!!
I was fixed this issue at my end. I update ui pom.xml file for npm and bower install with install --allow-root. :)

Apache drill 1.7 build failure

Trying to build apache drill from git clone https://git-wip-us.apache.org/repos/asf/drill.git
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Drill Root POM .............................. SUCCESS [ 13.700 s]
[INFO] tools/Parent Pom ................................... SUCCESS [ 2.708 s]
[INFO] tools/freemarker codegen tooling ................... SUCCESS [ 7.458 s]
[INFO] Drill Protocol ..................................... SUCCESS [ 16.764 s]
[INFO] Common (Logical Plan, Base expressions) ............ SUCCESS [ 13.602 s]
[INFO] Logical Plan, Base expressions ..................... SUCCESS [ 15.324 s]
[INFO] exec/Parent Pom .................................... SUCCESS [ 5.805 s]
[INFO] exec/memory/Parent Pom ............................. SUCCESS [ 1.478 s]
[INFO] exec/memory/base ................................... SUCCESS [ 10.578 s]
[INFO] exec/rpc ........................................... SUCCESS [ 4.130 s]
[INFO] exec/Vectors ....................................... SUCCESS [01:24 min]
[INFO] contrib/Parent Pom ................................. SUCCESS [ 1.237 s]
[INFO] contrib/data/Parent Pom ............................ SUCCESS [ 1.031 s]
[INFO] contrib/data/tpch-sample-data ...................... SUCCESS [ 4.037 s]
[INFO] exec/Java Execution Engine ......................... FAILURE [ 49.806 s]
[INFO] exec/JDBC Driver using dependencies ................ SKIPPED
[INFO] JDBC JAR with all dependencies ..................... SKIPPED
[INFO] contrib/kudu-storage-plugin ........................ SKIPPED
[INFO] contrib/mongo-storage-plugin ....................... SKIPPED
[INFO] contrib/hbase-storage-plugin ....................... SKIPPED
[INFO] contrib/jdbc-storage-plugin ........................ SKIPPED
[INFO] contrib/hive-storage-plugin/Parent Pom ............. SKIPPED
[INFO] contrib/hive-storage-plugin/hive-exec-shaded ....... SKIPPED
[INFO] contrib/hive-storage-plugin/core ................... SKIPPED
[INFO] contrib/drill-gis-plugin ........................... SKIPPED
[INFO] Packaging and Distribution Assembly ................ SKIPPED
[INFO] contrib/sqlline .................................... SKIPPED
[INFO] --------------------------------------------------------------------- ---
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:53 min
[INFO] Finished at: 2016-05-29T16:34:33+05:30
[INFO] Final Memory: 102M/795M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.
2:compile (default-compile) on project drill-java-exec: Compilation failure -> [
Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default- compile) on project drill-java-exec: Compilation failure
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.buildProje
ct(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre
adedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
356)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(Abstrac
tCompilerMojo.java:913)
at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.ja
va:129)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.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/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :drill-java-exec
My environment:
Maven version 3.3.9
Java version 1.7.0_45
Anyone who has faced such issues please give suggestions, solutions.
Even I got an issue few days back it saying Some unit tests are failing.
So i used mvn install -DskipTests to continue.
follow this link, i used git clone https://github.com/apache/drill.git repo.

Esper Tech Installation using Maven - No access on transport - Maybe jar issue?

I 've already read lot from your site, but it's the first time I really cannot find resolution for my problem through searching.
I try to install Esper Tech on Windows 8.1 with help of Maven 3.3. After many problems, I have this one too. It seems like a dependency problem between 2 source setting files of Esper.
Below my facts.
1.Maven's output (not all output but only for these 2 libraries)
[INFO] ----------------
[INFO] Building Esper Examples TerminalSvc - MDB 1.0
[INFO] ----------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) # example-terminalsvc-mdb ---
[INFO] Deleting C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) # example-terminalsvc-mdb ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) # example-terminalsvc-mdb ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[INFO] Compiling 8 source files to C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\target\classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) # example-terminalsvc-mdb ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\etc
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) # example-terminalsvc-mdb ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[INFO] Compiling 2 source files to C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\target\test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) # example-terminalsvc-mdb ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-war-plugin:2.2:war (default-war) # example-terminalsvc-mdb ---
[INFO] Packaging webapp
[INFO] Assembling webapp [example-terminalsvc-mdb] in [C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\target\example-terminalsvc-mdb-1.0]
[INFO] Processing war project
[INFO] Copying webapp resources [C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\src\main\webapp]
[INFO] Webapp assembled in [922 msecs]
[INFO] Building war: C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\target\example-terminalsvc-mdb-1.0.war
[INFO]
[INFO] --- maven-install-plugin:2.4:install (default-install) # example-terminalsvc-mdb ---
[INFO] Installing C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\target\example-terminalsvc-mdb-1.0.war to C:\Users\marianna\.m2\repository\com\espertech\example-terminalsvc-mdb\1.0\example-terminalsvc-mdb-1.0.war
[INFO] Installing C:\Users\marianna\esper-master\examples\terminalsvc\terminalsvc-mdb\pom.xml to C:\Users\marianna\.m2\repository\com\espertech\example-terminalsvc-mdb\1.0\example-terminalsvc-mdb-1.0.pom
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Esper Examples TerminalSvc - EAR 1.0
[INFO] ------------------------------------------------------------------------
Downloading: https://repo.maven.apache.org/maven2/com/espertech/example-terminalsvc-mdb/1.0/example-terminalsvc-mdb-1.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Esper .............................................. SUCCESS [02:52 min]
[INFO] EsperIO-AMQP ....................................... SUCCESS [ 16.781 s]
[INFO] EsperIO-CSV ........................................ SUCCESS [ 6.984 s]
[INFO] EsperIO-DB ......................................... SUCCESS [ 4.047 s]
[INFO] EsperIO-HTTP ....................................... SUCCESS [ 6.438 s]
[INFO] EsperIO-Socket ..................................... SUCCESS [ 3.078 s]
[INFO] EsperIO-SpringJMS .................................. SUCCESS [ 13.187 s]
[INFO] EsperIO-Stax ....................................... SUCCESS [ 5.032 s]
[INFO] Esper Examples ..................................... SUCCESS [ 0.062 s]
[INFO] Esper Examples - AutoID ............................ SUCCESS [ 1.516 s]
[INFO] Esper Examples - Benchmark ......................... SUCCESS [ 2.015 s]
[INFO] Esper Examples - CycleDetect ....................... SUCCESS [ 1.485 s]
[INFO] Esper Examples - MarketDataFeed .................... SUCCESS [ 1.312 s]
[INFO] Esper Examples - MatchMaker ........................ SUCCESS [ 1.656 s]
[INFO] Esper Examples - NamedWinQuery ..................... SUCCESS [ 0.985 s]
[INFO] Esper Examples - OHLCPlugInView .................... SUCCESS [ 1.265 s]
[INFO] Esper Examples - QualityOfServiceSLA ............... SUCCESS [ 1.313 s]
[INFO] Esper Examples - RFIDAssetZone ..................... SUCCESS [ 2.297 s]
[INFO] Esper Examples - RuntimeConfig ..................... SUCCESS [ 1.062 s]
[INFO] Esper Examples - ServerShell ....................... SUCCESS [ 1.500 s]
[INFO] Esper Examples - StockTicker ....................... SUCCESS [ 1.172 s]
[INFO] Esper Examples TerminalSvc - Common ................ SUCCESS [ 0.516 s]
[INFO] Esper Examples TerminalSvc - Receiver .............. SUCCESS [ 0.359 s]
[INFO] Esper Examples TerminalSvc - Sender ................ SUCCESS [ 0.625 s]
[INFO] Esper Examples TerminalSvc - MDB ................... SUCCESS [ 4.547 s]
[INFO] Esper Examples TerminalSvc - EAR ................... FAILURE [ 7.672 s]
[INFO] Esper Examples TerminalSvc ......................... SKIPPED
[INFO] Esper Examples - TerminalServiceJSE ................ SKIPPED
[INFO] Esper Examples - Transaction ....................... SKIPPED
[INFO] Esper Examples - Trivia Geeks Club ................. SKIPPED
[INFO] Esper .............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:20 min
[INFO] Finished at: 2015-12-22T14:06:23+02:00
[INFO] Final Memory: 71M/350M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project example-terminalsvc-ear: Could not resolve dependencies for project com.espertech:example-terminalsvc-ear:ear:1.0: Could not transfer artifact com.espertech:example-terminalsvc-mdb:jar:1.0 from/to local-repository (~/.m2/repository): Cannot access ~/.m2/repository with type default using the available connector factories: BasicRepositoryConnectorFactory: Cannot access ~/.m2/repository using the registered transporter factories: WagonTransporterFactory: Unsupported transport protocol -> [Help 1]
[ERROR]
2.My command for compilation is below:
mvn clean install -DskipTests=true -Dgpg.skip=true > log.txt
(gpg was my first big problem)
3.pom.xml from last project 'Esper Examples TerminalSvc - EAR' for dependency part
<dependencies>
<dependency>
<groupId>com.espertech</groupId>
<artifactId>example-terminalsvc-mdb</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
Steps I took to search issue:
rights on ./~m2/repository -> i made it public (not good tactic I know)
download manually .jar and paste it on target folder. But link has 404 error!
I tried to figure out why .jar is not found after it's project compilation. But this compilation has as a result .war not .jar
What could I miss?
Thanks a lot for your help!!
on the examples parent pom level (~/esper/examples/terminalsvc/) try to do
mvn clean package -DskipTests=true
The project builds fine.
INFO] --- maven-clean-plugin:2.5:clean (default-clean) # esper-terminalsvc ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Esper Examples TerminalSvc - Common ................ SUCCESS [ 9.449 s]
[INFO] Esper Examples TerminalSvc - Client ................ SUCCESS [ 0.298 s]
[INFO] Esper Examples TerminalSvc - Receiver .............. SUCCESS [ 0.101 s]
[INFO] Esper Examples TerminalSvc - MDB ................... SUCCESS [ 0.581 s]
[INFO] Esper Examples TerminalSvc - EAR ................... SUCCESS [ 0.811 s]
[INFO] Esper Examples TerminalSvc ......................... SUCCESS [ 0.002 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.382 s
[INFO] Finished at: 2015-12-23T13:29:26+01:00
[INFO] Final Memory: 22M/229M
Update
Please edit the file /esper/examples/terminalsvc/terminalsvc-ear/pom.xml and add the line war on the dependency, as shown below :
<dependencies>
<dependency>
<groupId>com.espertech</groupId>
<artifactId>example-terminalsvc-mdb</artifactId>
<version>1.0</version>
<type>war</type>
</dependency>
</dependencies>

Resources