Apache Maven is a Software Project Management tool. Based on the concept of a Project Object Model (POM), Maven can manage a project’s build, reporting and documentation from a central piece of information.
On Crunchify, we do have more than ~20 different maven tutorials including Setting up Maven Classpath on Windows and MacOS, maven-war-plugin, maven-shade-plugin, maven-assembly-plugin, etc.
In this tutorial we will go over highly and widely used some tips and tricks which will fix most of the Maven and POM dependency related issues for your in Eclipse IDE.
Below tips will work if you have any of below questions:
- In Java how to fix Maven, Maven Configuration and Maven Dependency issue?
- How do I update my Maven project to work in Eclipse?
- maven dependency problem in eclipse
- maven dependency problem eclipse missing artifact
- How to fix error “Updating Maven Project”?
- Maven Common Problems And Solutions
Let’s get started:
Task-1: Perform “Project Clean” in Eclipse IDE
Step-1
Create newmaven based project oropen existingmaven project.- In my case, I’m opening my existing Simplest Spring MVC Hello World Project in Eclipse.
Step-2
- Click on
ProjectMenu item in Eclipse - Choose
Clean...option from list
Step-3
- Select a
projectwhich you want to clean or Select All - In my case it’s just CrunchifySpringMVCTutorial
Task-2: Perform Maven Update Project in Eclipse IDE
Step-4
- Right click on Project
- Click on
Maven - Click on
Update Project...
Task-3: Perform Maven clean install in Eclipse IDE
Step-5
- Right click on project
- Click on
Run As - Click on
Maven build...
Step-6
- Provide Goal:
mvn clean install - Select checkbox for
Skip Tests - Click
ApplyandRun
You should see BUILD SUCCESS message after successful run.
By performing above steps most of the common Maven build issues should be resolved in Eclipse. Let me know if you face any more issues and will try to debug.
Last Option:
Nothing worked and you are still getting
weird Maven issue? Try deleting.m2/repository folder via File Explorer.-> After that perform above steps and all maven libraries will be downloaded again fresh.
Hi Sir,
When I import existing maven project(simple spring MVC project) I am getting “Cannot access defaults field of Properties” in order to avoid this i added maven war plugin 3.3.1 in pom.xml it got solved and I tried maven clean install in eclipse the build got failed… I am using STS 4 with jdk 17… Could you help me with this one
HI, App Shah. I can use clean install successfully but I can’t use mvn clean install. And I had already tried to delete the things in .m2/repository. And this is my problem. Th https://uploads.disquscdn.com/images/df6e972149fddb5c7f2a7474a986bf95a245995db99f87ff9f44515b0b11462b.jpg ank you!!!
HI, I have error with build failure, below is that
Hi Lavanya – this seems like an issue with mvn command.
Could you please try without MVN? i.e.
clean installinstead ofmvn clean install?[ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? [INFO] 1 error [INFO] ------------------------------------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.083 s [INFO] Finished at: 2020-09-08T02:43:30+05:30 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project Exam: Compilation failure [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project Exam: Compilation failure No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289) at org.apache.maven.cli.MavenCli.main(MavenCli.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347) Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1220) at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:187) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210) ... 20 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/MojoFailureExceptionI got this type of error when try to build the project.
Hi Sagar – could you please help share a screenshot of an error? It looks like you have just provided JRE as your classpath and not JDK.
Make sure to add JDK to your class path and retry.
Hope this helps.
Thanks – this post saved me a lot of problems after an mvn clean led to class not found errors.
You are welcome Jason. Happy to help. Happy coding and keep visiting.
Thanks a lot. after a long search and debug. this worked
Aaaha! Happy to help Chaitanya. Thanks for your feedback and comment.
hi sir, build is successfull but still i am getting error in pom.xml, i also deleted m2/reposiotry from file explorer,
Hi Abinash – after build success message, please try refreshing your project. Error in pom.xml may be just a temporary issue.
I am facing a problem while createing a maven project it take too long time and show somethimg dowloading but it look like stoped at point what i do
https://uploads.disquscdn.com/images/c543acf2dba26f99784ff4ee1ef0ef1190a349a2833d321f91f4f0ea42a14941.png
Hi Abinash – please see my comment here: http://disq.us/p/2a9lb6w
Hey Hi still I am getting this error after following your steps can help me to relove this?
Sorry to hear that Mallu Manish Shetty. Do you have Maven installed and is it in classpath?
Also one more thing. This seems like an issue with maven settings.xml file.
Could you please share file content?
APPLICATION FAILED TO START
***************************
Description: Failed to bind properties under '' to com.zaxxer.hikari.HikariDataSource: Property: driverclassname Value: org.postgresql.Driver Origin: "driverClassName" from property source "source" Reason: Failed to load driver class org.postgresql.Driver in either of HikariConfig class loader or Thread context classloader Action: Update your application's configuration [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17.715 s [INFO] Finished at: 2020-01-10T23:11:22+05:45 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.2.2.RELEASE:run (default-cli) on project demo: Application finished with exit code: 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/MojoExecutionExceptionwhat is the solution for this??
Shanti – Also try deleting your maven repository location. Building project will auto download all new dependencies.
Path: /Users//.m2/repository
You can find more details about setting.xml file and repository location here.
Hi Shanti – can you please try running maven clean install again?
Hope you have this dependency in your pom.xml:
Usually this error caused by Maven downloading a corrupt version of the jar. Deleting it to force a new download fixed the issue.
Nice Blog. Thanks for sharing such a nice details..
You are welcome Aveesha. Happy coding and keep visiting.
Hi I am facing error while I am trying to clean my maven project
Hi Divya – could you give me complete stack trace or exception message? Which error are you referring?
Getting this error:
Seems like an issue with Maven.
mvnis not available for you to use. Try – usingmaveninstead.-X clean install try this one
Try checking command one more time. As mentioned by Balu – try adding
-X option.Unknown lifecycle phase “mvn”. You must specify a valid lifecycle phase or a goal in the format : or :[:]:. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
Hi David – try removing mvn. Just use “clean install” and let me know if that works.
Unknown lifecycle phase “mvn”. You must specify a valid lifecycle phase or a goal in the format : or :[:]:. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
Hi Asif – try using clean install