'Plugin execution not covered by lifecycle configuration' error in product POM
From #158 (comment 371945):
I now notice the org.eclipse.escet.product\pom.xml file has the following error/warning (depending on your Maven Errors/Warnings setting)
Plugin execution not covered by lifecycle configuration: org.eclipse.tycho:target-platform-configuration:2.5.0:target-platform (execution: default-target-platform, phase: initialize) I'm not sure how 'bad' that is, do you?
The background of this message is explained here: https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html. It seems m2eclipse does not have the necessary metadata that it requires to know how to handle this plugin.
For me it shows as an error. I don't think we should have errors in our workspace. We should thus address this.
This wasn't a problem before, and it is now. I assume this is caused by moving from Tycho 2.3 to Tycho 2.5 as part of #158 (closed).
According to https://www.eclipse.org/tycho/sitedocs/target-platform-configuration/target-platform-configuration-mojo.html:
target-platform-configuration:target-platform-configuration
Full name: org.eclipse.tycho:target-platform-configuration:2.5.0:target-platform-configuration
Description: Configures the target-platform to use in order to resolve dependencies.
⚠️ This mojo is actually not executable, and is only meant to host configuration
It thus seems this is not meant to execute. Somehow metadata should indicate this plugin execution should have action ignore
.
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html indicates that:
Metadata Source Lookup Order
M2Eclipse considers lifecycle mapping metadata sources in the following order:
- The project’s pom.xml
- The parent pom.xml, the grand-parent pom.xml and so on.
- M2Eclipse 1.2+ workspace preferences (see below)
- Installed M2Eclipse extensions (in no particular order)
- M2Eclipse 1.1+ lifecycle mapping metadata provided by maven plugin (see below)
- Default lifecycle mapping metadata shipped with M2Eclipse
M2Eclipse uses the first applicable mapping found.
There are thus various ways metadata can be contributed. I see the following potential solutions:
- Use the provided quick fix to add configuration to our POM to ignore this message. This would not be the ideal solution, but if all else fails, we can get rid of the error this way.
- Use the provided quick fix to add configuration to our workspace to ignore this message. And add it to our Oomph setup. I would prefer adding it to the POM instead, to keep Maven-related configuration in the POM files.
- Upgrade to Eclipse 2021-12 to see whether it includes some plugin that provides the necessary metadata.
- Upgrade to a newer version of m2eclipse to see whether it has the necessary metadata.
I would hope upgrading Eclipse or m2eclipse solves this problem. If it doesn't, or even in the mean time, we could opt for the extra configuration in our POM file.