redhat-developer / redhat-developer/vscode-java
Fix or allow for workaround with classic bug "Plugin execution not covered by lifecycle configuration"
Open
Nobody has claimed this yet.
compile
diagnostics
enhancement
Maven
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Describe the bug
This is an old classic bug:
- https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
- https://stackoverflow.com/questions/6352208/how-to-solve-plugin-execution-not-covered-by-lifecycle-configuration-for-sprin
Expected Result
Not shown as a problem in the Problems tab. It looks as there is a solution for Eclipse (see 1 above).
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked m2e execution-not-covered documentation and the referenced Stack Overflow discussion to understand the reported Maven lifecycle warning. Reproduce the scenario shown in the issue and verify that the execution no longer appears as a problem in the Problems tab, or that the documented workaround is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100