redhat-developer / redhat-developer/vscode-java

Inadequate errror message - Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available.

Open
#726 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Maven
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

VS Code extension emits an inadequate error message Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available. To enable full functionality, install the lifecycle mapping and run Maven->Update Project Configuration. whenever the underlying service has a problem with an internal error (see https://github.com/eclipse/eclipse.jdt.ls/issues/866)

Environment
  • Operating System: Linux Fedora 29
  • JDK version: 10.0.2
  • Visual Studio Code version: 0.34.0
  • Java extension version: ???
Steps To Reproduce

See https://github.com/eclipse/eclipse.jdt.ls/issues/866 for producing an internal error in Eclipse base.

Current Result

Error message: "Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available."

Expected Result

Error message: Internal error in language service (+ actionable steps for reporting / diagnosing)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the internal-error reproduction described in eclipse/jdt.ls#866 and trace where the lifecycle-mapping message is emitted in the VS Code extension. Done means the extension reports an internal language-service error with actionable steps for reporting or diagnosis instead of the misleading lifecycle-mapping message.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.