Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Regular error "Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available" #115
Describe the bug
The strangest thing is that it happens when there were no updates in pom.xml or any other project-level files, when I am just editing *.java files. Sometimes it happens at the same time when "Language Support for Java" extension has issues parsing the files and dumps some errors in the log.
Also, "Maven->Update Project Configuration" (and Shift+Alt+U) works for me only if I have pom.xml open and it's window is active (which is unexpected).
Even "Maven->Update Project Configuration" does not always work for me.
First I typically need to fix all Java compilation issues and then I need to re-open VSCode and let it sit for a few minutes - then "Update Project Configuration" will start working. Sometimes I need to restart VSCode 2 or 3 times to finally make it work though.
Since VSCode restart fixes the issue - the recommendation to "install the lifecycle mapping" is pretty misleading in the message.
Environments (please complete the following information as much as possible):
referenced this issue
Aug 2, 2018
It looks this error is reported by m2e integrated in the language server, and here is not the best place for the issue.
Sometimes you are supposed to close VSCode before you delete the
I just created a same issue in the "Language Support for Java" extension, so I'm now closing it and you can track this in redhat-developer/vscode-java#603