Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 351332

Summary: IDE Specific POM pollution
Product: z_Archived Reporter: Adam Gray <adam.j.gray>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: matthew
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Adam Gray CLA 2011-07-06 10:00:26 EDT 
Build Identifier: 3.7

Is there really no other way to denote plugin executions as permanently ignored than to pollute the pom with IDE-specific blocks of xml?  Eclipse itself uses separate files for stuff like this.  I don't see why m2e should be any different.  I could understand if it could also be used by netbeans or idea or even the maven command-line itself.  In a development environment with 3 different IDE's represented, I really don't want to have to check in this stuff or manage it manually to keep it not checked in.

Reproducible: Always

Steps to Reproduce:
1. Permanently ignore plugin execution
2. POM gets edited with m2e settings/flags
Comment 1 Matthew Piggott CLA 2011-07-06 10:03:01 EDT 

*** This bug has been marked as a duplicate of bug 350414 ***
Comment 2 Denis Roy CLA 2021-04-19 13:24:55 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/