I have created very very basic spring boot project which is running locally, When i am trying to deploy on Heroku the build is failing .
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.123 s
[INFO] Finished at: 2021-11-19T10:39:40Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project GymMgmt: Fatal error compiling: invalid target release: 11 -> [Help 1]
Related
Good evening, im trying to install vaadin framework and integrate it into my eclipse but everytime i try to run the maven build i keep getting this error block, the main part is that the prefix jetty is not recognized and im not sre how to deal with that. Please help
[INFO] Scanning for projects...
[WARNING] The project com.gmail.khaled:my-starter-project:pom:1.0-SNAPSHOT uses prerequisites which is only intended for maven-plugin projects but not for non maven-plugin projects. For such purposes you should use the maven-enforcer-plugin. See https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] My Starter Project [pom]
[INFO] My Starter Project-backend [jar]
[INFO] My Starter Project-ui [war]
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloading from : https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading from : https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloaded from : https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml (14 kB at 13 kB/s)
[INFO] Downloaded from : https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (20 kB at 18 kB/s)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] My Starter Project 1.0-SNAPSHOT .................... SKIPPED
[INFO] My Starter Project-backend ......................... SKIPPED
[INFO] My Starter Project-ui 1.0-SNAPSHOT ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.739 s
[INFO] Finished at: 2019-03-18T21:39:18+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'jetty' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\hp\.m2\repository), vaadin-prereleases (https://maven.vaadin.com/vaadin-prereleases), 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/NoPluginFoundForPrefixException
This error message tells, that there is no maven Jetty plugin defined in the pom.xml where you are trying to run jetty:run target. Hence it is failing. Usually the convention in multi module maven projects is to place Jetty plugin to actual application module. In your case it is probably the "My Starter Project-ui" module. If it is not there you need to add it there.
I had the same problem. When creating a debug configuration in the field goal
do not type: jetty:run
instead type: spring-boot:run
I'm using Vaadin and the vaadin-maven-plugin to build a project with front files.
When I am running the goal locally I have no errors and the project builds successfully:
[INFO] Installed Yarn locally.
[INFO] Running 'yarn install' in /home/kaa/Documents/Projects/limitmanager.front/target
[INFO] yarn install v1.6.0
[INFO] [1/4] Resolving packages...
[ERROR] warning babel-preset-env > browserslist#2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[INFO] [2/4] Fetching packages...
[INFO] [3/4] Linking dependencies...
[ERROR] warning "polymer-build > polymer-project-config#3.13.0" has incorrect peer dependency "polymer-analyzer#^3.0.0-pre.17 || ^3.0.0".
[INFO] [4/4] Building fresh packages...
[INFO] success Saved lockfile.
[INFO] Done in 7.12s.
[INFO] Processing frontend files from '/home/kaa/Documents/Projects/limitmanager.front/target/frontend'
[INFO] Running 'gulp build_es6' in /home/kaa/Documents/Projects/limitmanager.front/target
[INFO] [12:28:51] Using gulpfile ~/Documents/Projects/limitmanager.front/target/gulpfile.js
[INFO] [12:28:51] Starting 'build_es6'...
[INFO] Deleting /home/kaa/Documents/Projects/limitmanager.front/target/classes/META-INF/resources/frontend-es6 directory...
[INFO] [12:28:51] Finished 'build_es6' after 5.17 ms
[INFO] Starting to process frontend files.
[INFO] Will minify frontend files.
[INFO] Will bundle frontend files.
[INFO] Will hash bundle file names.
[INFO] Will copy files to target directory '/home/kaa/Documents/Projects/limitmanager.front/target/classes/META-INF/resources/frontend-es6'.
[INFO] Starting operations stated above, this might take a while.
[INFO] Writing bundle manifest to '/home/kaa/Documents/Projects/limitmanager.front/target/classes/META-INF/resources/frontend-es6/vaadin-flow-bundle-manifest.json'
But, running on gitlab CI causes an error:
Caused by: com.github.eirslett.maven.plugins.frontend.lib.ProcessExecutionException: java.io.IOException: Cannot run program "/bcsbankms/limitmanager.front/target/node/node" (in directory "/bcsbankms/limitmanager.front/target"): error=2, No such file or directory
Part of the log:
57389 [ERROR] warning "polymer-build > polymer-project-config#3.13.0" has incorrect peer dependency "polymer-analyzer#^3.0.0-pre.17 || ^3.0.0".
59986 [INFO] [4/4] Building fresh packages...
60052 [INFO] success Saved lockfile.
60055 [INFO] Done in 34.04s.
60071 [INFO] Processing frontend files from '/bcsbankms/limitmanager.front/target/frontend'
60086 [INFO] Running 'gulp build_es6' in /bcsbankms/limitmanager.front/target
60091 [INFO] ------------------------------------------------------------------------
60091 [INFO] BUILD FAILURE
60091 [INFO] ------------------------------------------------------------------------
60093 [INFO] Total time: 59.119 s
60093 [INFO] Finished at: 2018-10-05T05:54:08Z
60094 [INFO] ------------------------------------------------------------------------
60094 [ERROR] Failed to execute goal com.vaadin:vaadin-maven-plugin:11.0.0:package-for-production (default) on project ru.bcs.bank.ms.limitmanager.front: Execution default of goal com.vaadin:vaadin-maven-plugin:11.0.0:package-for-production failed: Transpilation with gulp has failed: 'gulp build_es6' failed. java.io.IOException: Cannot run program "/bcsbankms/limitmanager.front/target/node/node" (in directory "/bcsbankms/limitmanager.front/target"): error=2, No such file or directory -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.vaadin:vaadin-maven-plugin:11.0.0:package-for-production (default) on project ru.bcs.bank.ms.limitmanager.front: Execution default of goal com.vaadin:vaadin-maven-plugin:11.0.0:package-for-production failed: Transpilation with gulp has failed
This is a known issue.
As far as i know, you can ignore it.
Siafu is a context simulator
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] MavenParent ........................................ SUCCESS [ 0.004 s]
[INFO] Siafu Simulator .................................... FAILURE [01:27 min]
[INFO] Siafu datatypes library ............................ SKIPPED
[INFO] Simulation-Glasgow ................................. SKIPPED
[INFO] Simulation-Leimen .................................. SKIPPED
[INFO] Simulation-Office .................................. SKIPPED
[INFO] Simulation-Testland ................................ SKIPPED
[INFO] Simulation-Valencia ................................ SKIPPED
[INFO] Simulations ........................................ SKIPPED
[INFO] SiafuAggregator .................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:27 min
[INFO] Finished at: 2017-04-24T15:45:12+08:00
[INFO] Final Memory: 10M/91M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project Siafu: Could not resolve dependencies for project Siafu:Siafu:jar:1.0.6-SNAPSHOT:
Failed to collect dependencies at org.eclipse.swt:org.eclipse.swt.gtk.linux.x86:jar:3.8:
Failed to read artifact descriptor for org.eclipse.swt:org.eclipse.swt.gtk.linux.x86:jar:3.8:
Could not transfer artifact org.eclipse.swt:org.eclipse.swt.gtk.linux.x86:pom:3.8 from/to swt-repo (https://swt-repo.googlecode.com/svn/repo/): Network is unreachable (connect 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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf
Please give me some help to solve this problem,thanks!
I am trying to build the Californium repository https://github.com/eclipse/californium using maven. Typing "mvn clean install" gives the following output:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.eclipse.californium:californium-core:jar:1.0.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-surefire-plugin is missing. # line 29, column 18
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Californium (Cf) Root
[INFO] Californium (Cf) Core
[INFO] Californium (Cf) Proxy
[INFO] Californium (Cf) OSGi Bundle
[INFO] Cf-PlugtestClient
[INFO] Cf-PlugtestChecker
[INFO] Cf-PlugtestServer
[INFO] Cf-HelloWorldClient
[INFO] Cf-HelloWorldServer
[INFO] Cf-SecureServer
[INFO] Cf-ExampleCrossProxy
[INFO] Cf Benchmark Server
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Californium (Cf) Root 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.eclipse.californium:element-connector:jar:1.0-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Californium (Cf) Root ............................. FAILURE [0.097s]
[INFO] Californium (Cf) Core ............................. SKIPPED
[INFO] Californium (Cf) Proxy ............................ SKIPPED
[INFO] Californium (Cf) OSGi Bundle ...................... SKIPPED
[INFO] Cf-PlugtestClient ................................. SKIPPED
[INFO] Cf-PlugtestChecker ................................ SKIPPED
[INFO] Cf-PlugtestServer ................................. SKIPPED
[INFO] Cf-HelloWorldClient ............................... SKIPPED
[INFO] Cf-HelloWorldServer ............................... SKIPPED
[INFO] Cf-SecureServer ................................... SKIPPED
[INFO] Cf-ExampleCrossProxy .............................. SKIPPED
[INFO] Cf Benchmark Server ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.894s
[INFO] Finished at: Thu Jun 26 18:29:52 CEST 2014
[INFO] Final Memory: 6M/109M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project root: Could not resolve dependencies for project org.eclipse.californium:root:pom:1.0.0-SNAPSHOT: Could not find artifact org.eclipse.californium:element-connector:jar:1.0-SNAPSHOT -> [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 tried different things but still Idon't know how to fix this errors and go on with my work. Can anyone help me?
MORE INFO:
Downloding and installing (mvn clean install) Californium Element Connector https://github.com/eclipse/californium.element-connector.git brings the build of Californium a little farther, but there are still some dependencies missing. I think that one of these is californium Scandium, but after I downloaded it, I found out that it also has some building problems...
Actually, all I want to use is the repo caled californium.tools (https://github.com/eclipse/californium.tools), which is based on Californium. I checked the pom.xml of californium.tools, and it already includes the required dependencies. However,when I build, I get the following errors:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Californium (Cf) Tools
[INFO] Cf-ConsoleClient
[INFO] Cf-GUIClient
[INFO] Cf-CoAPBench
[INFO] Cf-ExampleServer
[INFO] Cf-ResourceDirectory
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Californium (Cf) Tools 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) # tools ---
[INFO] Deleting file set: /home/ceccog/californium.tools/target (included: [**], excluded: [])
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) # tools ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/ceccog/californium.tools/target/tools-1.0.0-SNAPSHOT-tests.jar
[INFO]
[INFO] >>> maven-source-plugin:2.2.1:jar (attach-sources) # tools >>>
[INFO]
[INFO] <<< maven-source-plugin:2.2.1:jar (attach-sources) # tools <<<
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) # tools ---
[INFO]
[INFO] --- maven-install-plugin:2.3:install (default-install) # tools ---
[INFO] Installing /home/ceccog/californium.tools/pom.xml to /home/ceccog/.m2/repository/org/eclipse/californium/tools/1.0.0-SNAPSHOT/tools-1.0.0-SNAPSHOT.pom
[INFO] Installing /home/ceccog/californium.tools/target/tools-1.0.0-SNAPSHOT-tests.jar to /home/ceccog/.m2/repository/org/eclipse/californium/tools/1.0.0-SNAPSHOT/tools-1.0.0-SNAPSHOT-tests.jar
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Cf-ConsoleClient 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.eclipse.californium:scandium:jar:1.0.0-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Californium (Cf) Tools ............................ SUCCESS [0.886s]
[INFO] Cf-ConsoleClient .................................. FAILURE [0.078s]
[INFO] Cf-GUIClient ...................................... SKIPPED
[INFO] Cf-CoAPBench ...................................... SKIPPED
[INFO] Cf-ExampleServer .................................. SKIPPED
[INFO] Cf-ResourceDirectory .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.161s
[INFO] Finished at: Wed Jul 02 11:42:57 CEST 2014
[INFO] Final Memory: 7M/111M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project cf-client: Could not resolve dependencies for project org.eclipse.californium:cf-client:jar:1.0.0-SNAPSHOT: Could not find artifact org.eclipse.californium:scandium:jar:1.0.0-SNAPSHOT -> [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 <goals> -rf :cf-client
EDIT: it looks like the maven repositories are online now and the bug in cf-secure has been fixed. So only step 4 is required to install the californium tools.
The repositories mentioned in README.md do not seem to be online yet. Therefore maven can not resolve the dependencies automatically. The trick is to build and install the maven artifacts directly from source in the appropriate order.
So in order to get californium.tools working:
install org.eclipse.californium:element-connector
git clone https://github.com/eclipse/californium.element-connector.git
cd californium.element-connector
mvn clean install
install org.eclipse.californium:scandium
git clone https://github.com/eclipse/californium.scandium.git
cd californium.scandium
mvn clean install
install org.eclipse.californium:californium-core
git clone https://github.com/eclipse/californium.git
cd californium
mvn -pl :californium-core -am clean install
Note that we are only building the californium-core submodule (with the -pl :californium-core -am flag), since there is a bug in cf-secure which causes the build to fail.
build the Californium tools
git clone https://github.com/eclipse/californium.tools.git
cd californium.tools
mvn -pl :cf-browser,:cf-coapbench,:cf-rd,:cf-server -am clean install
We need to exclude cf-client since it has a bug which makes the build fail.
To run any of the tools, just cd californium.tools/run and java -jar ... the appropriate jar.
Sorry, the project was recently created at eclipse.
Hudson is populating the maven repository now.
I'm just getting started with jersey and have built the jersey 2.0 skeleton webapp using maven.
The command being:
mvn archetype:generate -DarchetypeGroupId=org.glassfish.jersey.archetypes \
-DarchetypeArtifactId=jersey-quickstart-webapp -DarchetypeVersion=2.0
Now if I try to execute this using mvn clean exec:java I get the following error:
[INFO] ------------------------------------------------------------------------
[INFO] Building testwebservice 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) # testwebservice ---
[INFO] Deleting /Volumes/data/Projects/TestWebService/testwebservice/target
[INFO]
[INFO] >>> exec-maven-plugin:1.2.1:java (default-cli) # testwebservice >>>
[INFO]
[INFO] <<< exec-maven-plugin:1.2.1:java (default-cli) # testwebservice <<<
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:java (default-cli) # testwebservice ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.627s
[INFO] Finished at: Sat Jun 22 17:46:18 CEST 2013
[INFO] Final Memory: 8M/125M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default-cli) on project testwebservice: The parameters 'mainClass' for goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java are missing or invalid -> [Help 1]
The help provided isn't very helpful and I can't seem to find anything about this on the web. I have no clue where to set the parameters mainClass for "goal" (whatever that means) org.codehaus... . This is my first maven project and I'm pretty lost
Thanks for the help guys
You have generated a WEB Project and you are trying to run a java Application.
If you have a look at the Exec Plungin Documentation you will find that it requires an mainClassargument
and that's what the error message tells you
The parameters 'mainClass' for goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:java are missing or invalid
But as I've already written you have generated a WEB Application Skeleton running it as Java Application does not really make sense.
Have a look at Building Simple Jersey Web App With Maven to find out what you'll have to do to get your web application running.
Try to run the following command using command line by going inside your project directory:
mvn clean generate-sources package