Fix or allow for workaround with classic bug "Plugin execution not covered by lifecycle configuration"

[lfvjimisola]

Describe the bug

This is an old classic bug:

1. https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
2. 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

[RolKau]

The solution by Andrew White on the Stack Overflow page referred to above works for me in VS Code too (after you change the names and versions of the plugins of course); I put it in a

    <profile>
        <id>VSCode</id>
        <activation>
            <property><name>m2e.version</name></property>
        </activation>
        <!-- ... -->
    </profile>

so that it only affects the IDE and not any command-line builds.

[SergiuFM]

I have a similar problem and so far nothing of what was suggested above works.

My error in the "lowest" pom file is at this node:

<parent>  
  <groupId>ca.toronto.kogito.quarkus</groupId>
  <artifactId>ca-toronto-kogito-quarkus</artifactId>
  <version>1.41.0.Final</version>
</parent>

The error is:
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:check (execution: default, phase: validate)

I mention that I do not use Eclipse. I use VSCode as IDE.
The VSCode environment suggests either one of these 3 things but none of them solves the problem.

1. mark execution as ignored
2. enable execution in project configuration phase
3. enable execution in project build phase

Any help would be highly appreciated.
Thank you

[RolKau]

@SergiuFM
The error cannot be at the <parent> node; that is not the node that specifies the plugin. However, the name of the plugin is mentioned in the error message. You should have something like this fragment in your POM:

<pluginExecution>
   <pluginExecutionFilter>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-checkstyle-plugin</artifactId>
      <versionRange>[3.1.1,)</versionRange>
      <goals>
         <goal>check</goal>
      </goals>
   </pluginExecutionFilter>
   <action>
      <execute />
   </action>
</pluginExecution>

[SergiuFM]

@RolKau indeed the error was not at the parent node, it was just signaled/marked with a yellow bulb at the parent node. So that is very misleading in vscode.

Anyways, thanks to @RolKau, I managed to solve this error by adding at the gran-parent pom level the following entry:

<pluginManagement>
	<plugins>	 
		<plugin>
			<groupId>org.eclipse.m2e</groupId>
			<artifactId>lifecycle-mapping</artifactId>
			<version>1.0.0</version>
			<configuration>
				<lifecycleMappingMetadata>
					<pluginExecutions>
						<pluginExecution>
							<pluginExecutionFilter>
								<groupId>org.apache.maven.plugins</groupId>
								<artifactId>maven-checkstyle-plugin</artifactId>
								<versionRange>[3.1.1,)</versionRange>
								<goals>
									<goal>check</goal>
								</goals>
							</pluginExecutionFilter>
						<action>
							<ignore/>
						</action>
						</pluginExecution>
					</pluginExecutions>
				</lifecycleMappingMetadata>
			</configuration>
		</plugin>
	</plugins>
</pluginManagement>

Please note that I have added few more things on top of what @RolKau provided.
I cannot 100% say that my addition was necessary, but I am providing this information for the benefit of other people

Cheers

[RolKau]

@SergiuFM
Glad to have inspired you to find a solution to your problem. If you ever need to build the project outside of VS Code, for instance in Jenkins or Gitlab CI, I also encourage you to look at my comment above about putting this into a conditionally activated profile, as the lifecycle-mapping plugin is only virtual and does not exist on Maven Central.