ctubbsii commented on a change in pull request #64:
URL: https://github.com/apache/maven-apache-parent/pull/64#discussion_r787992599



##########
File path: pom.xml
##########
@@ -299,6 +299,32 @@ under the License.
           <artifactId>apache-rat-plugin</artifactId>
           <version>0.13</version>
         </plugin>
+        <!-- Disable execution of some plugins in m2e 
(https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html) -->
+        <plugin>
+          <groupId>org.eclipse.m2e</groupId>
+          <artifactId>lifecycle-mapping</artifactId>
+          <version>1.0.0</version>
+          <configuration>
+            <lifecycleMappingMetadata>
+              <pluginExecutions>
+                <pluginExecution>
+                  <!-- no native m2e support yet 
(https://issues.apache.org/jira/browse/MRRESOURCES-85) -->
+                  <pluginExecutionFilter>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-remote-resources-plugin</artifactId>
+                    <versionRange>[1.7.0,1.8.0)</versionRange>
+                    <goals>
+                      <goal>process</goal>
+                    </goals>
+                  </pluginExecutionFilter>
+                  <action>
+                    <ignore/>
+                  </action>
+                </pluginExecution>
+              </pluginExecutions>
+            </lifecycleMappingMetadata>
+          </configuration>
+        </plugin>

Review comment:
       I figure this section can just be deleted when the plugin version is 
bumped to one where support was added. But, if the metadata is added to do 
anything other than ignore inside the plugin itself, and the user specifies a 
newer version than what's in the parent POM here, then I guess you are right.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to