java - How to tell eclipse NOT to validate pom.xml without changing pom.xml? -
my pom.xml fine , can mvn clean install without problem eclipse paints reddish , complains about:
description resource path location type plugin execution not covered lifecycle configuration: org.jacoco:jacoco-maven-plugin:0.5.10.201208310627:prepare-agent (execution: default, phase: initialize) pom.xml /super-project line 11 maven project build lifecycle mapping problem how tell eclipse forget pom.xml, in other words, not seek compile it, validate it, etc. project not have errors , not painted in red?
i have had similar problem in past eclipse doesn't plugin in pom. solution i've found utilize plugin management. illustration own code is:
<pluginmanagement> <plugins> <!--this plugin's configuration used store eclipse m2e settings only. has no influence on maven build itself. --> <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.6,) </versionrange> <goals> <goal> copy-dependencies </goal> </goals> </pluginexecutionfilter> <action> <ignore /> </action> </pluginexecution> </pluginexecutions> </lifecyclemappingmetadata> </configuration> </plugin> </plugins> </pluginmanagement> it's messy, prevents future devs having same headaches.
official m2e page has way ignore them if running 4.2 juno
java eclipse maven m2eclipse jacoco
No comments:
Post a Comment