Description Alex McCarrier 2011-12-01 12:37:03 EST

I have a project that inherits from other POMs goals that appear to be incompatible with m2e.  Specifically, I have several "plugin execution not covered by lifecycle configuration" errors.  These are plugins that my company has built, and so there is no obvious lifecycle mapping.

In order to fix these errors by ignoring them, I have to modify the POM to do so.  In reality this is not an error with the POM, it is a perfectly valid POM and functions will from CLI, and other IDEs (Intellij, Netbeans).  It even functions fine in Eclipse, other than the fact that all my projects look like they are in error when they really aren't.

I suggest the following enhancement:

1 - Issues where the POM is valid, but m2e can't interpret it, should be flagged as a warning instead of an error.

2 - In order to fix these issues via an ignore clause, that clause should not be required in the pom, but in the eclipse project settings instead since the issue is not really with the POM, but with eclipse instead.

Bonus

3 - Provide a configuration setting so that the user can determine if m2e issues in the POM are warnings or errors, similar to how certain code issues can be configured as warnings or errors.