Description Adrian Shum 2011-10-04 03:00:30 EDT

Build Identifier: 

The current available way to customize the life cycle mapping, without writing new Project Configurator, is to add a bunch of config in POM for org.eclipse.m2e:lifecycle-mapping.  

However, it is not really a good idea to pollute the POM with IDE specific settings. And, the lifecycle mapping should depends more on the installation of Eclipse, instead of POM.  For example, it is totally reasonable that there are 2 developers having different eclipse plugins installed, one can make use of project configurator, while the other one decide he want to ignore certain maven plugin execution.  Current implementation of m2e seems unable to achieve this.

It will be much better if we can define the lifecycle mapping in Eclipse, either in the preference pane, or in a configuration file.

I am thinking if I can develop a custom m2e extension for this.  However, a brief search on the documentation seems suggest that, for an m2e extension, the mapped lifecycle is defined in a static lifecycle-mapping-metadata.xml.  Unless the extension can report its mapped lifecycle through runtime interface, there seems no way to make such kind of configuration possible.

Reproducible: Always