Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Contributing: Plugin execution not covered by lifecycle configuration

See original GitHub issue

I have been trying to load the Plugin source in a fresh install of Eclipse 2019-06 for Committers or Eclipse 2019-03 for Committers, following the usual steps as for the contibutors guide.

The project build within Eclipse seems to fail with the following error (multiple instances in org.eclipse.corrosion and org.eclipse.corrosion.tests).

Plugin execution not covered by lifecycle configuration: org.eclipse.tycho:tycho-compiler-plugin:1.4.0:compile (execution: default-compile, phase: compile)

Issue Analytics

State:
Created 4 years ago
Comments:13 (13 by maintainers)

Top GitHub Comments

1reaction

mickaelistriacommented, Jun 26, 2019

With https://github.com/eclipse/corrosion/commit/102d849542dc93df94799b7d789e403b12eb8559 , changing .settings shouldn’t require bumping the version as long as the change in .settings/ doesn’t result in different binary content.

1reaction

mickaelistriacommented, Jun 24, 2019

Plugin execution not covered by lifecycle configuration: org.eclipse.tycho:tycho-compiler-plugin:1.4.0:compile (execution: default-compile, phase: compile)

m2e should show a quickfix on those errors, like “Search for connectors” or something like that. By going through this process, you should be guided to installation of the m2e-tycho connector that would fix such issues. However, m2e-tycho doesn’t do much important things for LSP4E, so you may also just follow the quickfix that allows to skip this execution. Anyway, I think Tycho itself could improve that, I’ve opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=548569

[ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.4.1:wget (fetch-rustup-install-script) on project org.eclipse.corrosion: Execution fetch-rustup-install-script of goal com.googlecode.maven-download-plugin:download-maven-plugin:1.4.1:wget failed: java.lang.ClassNotFoundException: com.googlecode.download.maven.plugin.internal.CachedFileEntry -> [Help 1]

This one is nasty and is a bug in download-maven-plugin not properly handling version change because it reuses the cache in a former version and isn’t able to process it. To work around it, delete your .m2/repository/.cache/download-maven-plugin folder and retry a build.

Top Results From Across the Web

How to solve "Plugin execution not covered by lifecycle ...

Window > Preferences > Maven > Errors/Warnings > Plugin execution not covered by life-cycle configuration. Select Ignore / Warning / Error as your...

Execution Not Covered - M2Eclipse

Starting with M2Eclipse 1.2, it is now possible to configure lifecycle mapping metadata in m2e workspace preferences. Plugin goals can be ignored at...

Plugin execution not covered by lifecycle configuration ...

Phenonmenon When I importted the release of project into Eclipse, I had errors belows. They stopped Eclipse from importting it.

[SOLVED] "Plugin execution not covered by lifecycle ...

I wanted to start by saying I love OpenHAB and have been using it for my home setup for years now. It really...

"Plugin execution not covered by lifecycle configuration" for ...

The problem is some parent configures the maven-compiler-plugin to use compilerId=eclipse, which is not supported out of the box by m2e (it only...