How to solve the plugin execution not covered by lifecycle configuration: XXX plugin problem after converting the project to Maven project using m2e

From the official documentation http://wiki.eclipse.org/M2E_plugin_execution_not_covered, you can understand that the best solution is to hand over to the project aggregator dedicated to the plug-in for processing,
For example, the aspectj-Maven-plugin commonly used in the project uses a dedicated aggregator. You can use eclipse for online search and installation.
However, some plug-ins do not correspond to the project aggregator. At this time, we can only manually configure them to tell m2e how to handle the goal of these plug-ins during eclipse build. the following is a typical configuration: Ignore the goal related to the native2ascii and dependency plug-ins. you don't have to manually write this configuration. eclipse can generate it for you.

<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-dependency-plugin</artifactId><versionRange>[2.1,)</versionRange><goals><goal>unpack-dependencies</goal></goals></pluginExecutionFilter><action><ignore/></action></pluginExecution><pluginExecution><pluginExecutionFilter><groupId>org.codehaus.mojo</groupId><artifactId>native2ascii-maven-plugin</artifactId><versionRange>[1.0-alpha-1,)</versionRange><goals><goal>native2ascii</goal></goals></pluginExecutionFilter><action><ignore/></action></pluginExecution></pluginExecutions></lifecycleMappingMetadata></configuration></plugin>