i tried to build the zeppelin-0.7.0 master branch downloaded from github, but failed .
the build command:
mvn package -Pyarn -Pbuild-distr -Pspark-2.0 -Dspark.version=2.0.1 -Phadoop-2.6 -Dhadoop.version=2.6.0 -Pscala-2.11 -Ppyspark -DskipTests -X
the output stacktrace is:
[ERROR] error Command failed with exit code 1.
[INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 27.397 s
[INFO] Finished at: 2017-01-14T11:39:00+08:00
[INFO] Final Memory: 19M/228M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:yarn (yarn install) on project zeppelin-web: Failed to run task: 'yarn install --no-lockfile' failed. (error code 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:yarn (yarn install) on project zeppelin-web: 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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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: 'yarn install --no-lockfile' failed. (error code 1)
at com.github.eirslett.maven.plugins.frontend.lib.YarnTaskExecutor.execute(YarnTaskExecutor.java:61)
at com.github.eirslett.maven.plugins.frontend.mojo.YarnMojo.execute(YarnMojo.java:65)
at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:89)
... 22 more
[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
I found a lot but no info about this error. Thanks in advance for helping me figure out the reason.
Try to downgrade your node version to node 6 and compile again.
After compilation, upgrade your node version.
I hit the same issue-- I ended up installing all the various npm bits that kept failing by running:
$ sudo npm install -g bower grunt grunt-cli npm-run-all rimraf webpack
Also the build attempt didn't like that I ran it initially as sudo/root (on a test machine), so I recursively changed ownership of /opt/zeppelin (where I extracted the zeppelin tarball) to a regular user 'zeppelin', then ran the maven build command as user zeppelin at /opt/zeppelin. This was able to get me unblocked, hopefully this may help you too.
Related
I updated all architecture (Java17, Maven3, Spring 2.7/core5.3...) and Vaadin 23, but I can only run in development mode. I can no longer run -Pproduction. Build failure :
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33.260 s
[INFO] Finished at: 2022-08-31T11:35:42-03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.vaadin:flow-maven-plugin:23.1.6:build-frontend (default) on project template-module-app: Could not execute build-frontend goal: Error occured during goal execution: Cannot invoke "java.lang.Class.isInterface()" because the return value of "org.reflections.Reflections.forClass(String, java.lang.ClassLoader[])" is nullPlease run Maven with the -e switch (or Gradle with the --stacktrace switch), to learn the full stack trace. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.vaadin:flow-maven-plugin:23.1.6:build-frontend (default) on project template-module-app: Could not execute build-frontend goal
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:375)
I've tried everything:
https://vaadin.com/docs/latest/tools/mpr/configuration/production-mode
https://vaadin.com/docs/latest/tools/ce/going-to-production
https://vaadin.com/docs/latest/production/troubleshooting
...
I recently started studying Vaadin. At the beginning I am using Vaadin 8 and have started a small Vaadin project in eclipse for practice purposes. I always started and opened this project via Jetty on my localhost:8080. That worked great for the first few days, but since yesterday
my localhost:8080 wants username and password at once and the application is no longer opening there.
The only difference is that the day before yesterday I installed an Oracle database (OracleXE 11 g) - could that have something to do with it?
Here is a snipppet if the error-message that I am getting:
Sep. 12, 2021 10:51:20 VORM. org.atmosphere.cpr.AtmosphereFramework addInterceptorToAllWrappers
INFORMATION: Installed AtmosphereInterceptor Track Message Size Interceptor using | with priority BEFORE_DEFAULT
[INFO] Started o.e.j.m.p.JettyWebAppContext#60b616c8{/,file:///C:/Repositories/ProgrammingCourses/Vaadin-and-Maven_Crash-Course/VaadinFirstSteps/src/main/webapp/,AVAILABLE}{file:///C:/Repositories/ProgrammingCourses/Vaadin-and-Maven_Crash-Course/VaadinFirstSteps/src/main/webapp/}
[INFO] Jetty server exiting.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 42.520 s
[INFO] Finished at: 2021-09-12T10:51:20+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.3.9.v20160517:run (default-cli) on project VaadinFirstSteps: Failure: Address already in use: bind -> [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
Anyone know how to get Vaadin up and running again? I am grateful fur any help,
Zrebna :)
"Failure: Address already in use: bind" means that you are trying to start web application server on localhost port 8080 while there is already web application server running and owning that port. Hence new one cannot be started.
You need to check you processes already running and kill the old one.
I have a working GCP account and trying to run a dataflow job which ingest data from on-prem oracle to BigQuery using cloud SDK. I have installed the versioned cloud SDK tool and configured my account. I want to use the JDBCToBigQuery template.
Tried executing:
mvn compile exec:java -Dexec.mainClass=com.google.cloud.teleport.templates.JdbcToBigQuery -Dexec.cleanupDaemonThreads=false -Dexec.args="--driverJars=gs://********/jars/ojdbc8-8.0.17.jar --driverClassName=oracle.jdbc.OracleDriver --connectionURL=***** --query='select * from schema.users' --outputTable= ***** --bigQueryLoadingTemporaryDirectory=***** --username=***** --password=****** --project=***** --runner=DirectRunner"
It throws this error:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:24 min
[INFO] Finished at: 2019-11-21T23:02:45-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project google-cloud-teleport-java: An exception occured while executing the Java class. org.apache.beam.sdk.util.UserCodeException: java.lang.RuntimeException: java.io.IOException: Error reading gs://********/jars/ojdbc8-8.0.17.jar: connect timed out -> [Help 1]
I am working behind the company's proxy but have taken care of that by incorporating proxy settings.
Trying to troubleshoot this error, can anyone help out in this?
P.S.: Newbie to google cloud services
I have downloaded the spring data neo4j rest code from the following location
https://spring.io/guides/gs/accessing-neo4j-data-rest/
when I am running maven command to package I am getting following error.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building gs-accessing-neo4j-data-rest 0.1.0
[INFO] ------------------------------------------------------------------------
Downloading: https://repo.maven.apache.org/maven2/org/neo4j/neo4j-cypher-dsl/2.0.1/neo4j-cypher-dsl-2.0.1.pom
[WARNING] The POM for org.neo4j:neo4j-cypher-dsl:jar:2.0.1 is missing, no dependency information available
Downloading: https://repo.maven.apache.org/maven2/org/neo4j/neo4j-cypher-dsl/2.0.1/neo4j-cypher-dsl-2.0.1.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.861 s
[INFO] Finished at: 2015-08-04T03:53:47-04:00
[INFO] Final Memory: 14M/60M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project gs-accessing-neo4j-data-rest: Could not resolve dependencies for project org.springframework:gs-accessing-neo4j-data-rest:jar:0.1.0: Could not find artifact org.neo4j:neo4j-cypher-dsl:jar:2.0.1 in central (https://repo.maven.apache.org/maven2) -> [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
I don't know how to resolve this. can anybody help me with this.
Add the following section to main pom.xml so that Maven will be able to find and download missing artifact(s):
<repositories>
<repository>
<id>spring-releases</id>
<name>Spring Releases</name>
<url>https://repo.spring.io/libs-release</url>
</repository>
<repository>
<id>neo4j</id>
<name>Neo4j</name>
<url>http://m2.neo4j.org/</url>
</repository>
</repositories>
Hello I am trying to install Hue on AWS EC2 instance.
Following below link.
https://github.com/cloudera/hue
While doing step make apps I am getting below error.
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message:
Detected JDK Version: 1.6.0-30 is not in the allowed range [1.7.0,1.7.1000].
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.717s
[INFO] Finished at: Sun Mar 09 13:18:59 EDT 2014
[INFO] Final Memory: 5M/25M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce (default) on project hue-parent: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [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
I have java version
java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Additional information can be provided. Thanks for your help.
You can also remove the JDK 7 check by editing:
vim maven/pom.xml
And replacing the '7' by '6':
<javaVersion>1.7</javaVersion>
<sourceJavaVersion>1.7</sourceJavaVersion>
<targetJavaVersion>1.7</targetJavaVersion>
(obviously you should it might be better to make sure Java 7 is the default if you plan to use 7)
It looks like you have another Java version in your system too. Based on what your installation says:
Detected JDK Version: 1.6.0-30
Make sure your JAVA_HOME variable points to the home of your Java 1.7 installation.