|Re: [m2e-users] Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)|
On 11-11-07 5:39 AM, Guillaume Polet wrote:
Lifecycle configuration in pom.xml is tracked as . m2e development team does not have immediate plans to implement this feature for the reasons I explained in the bugzila but we will accept a quality patch that implements this feature. I will be happy to provide more detailed requirements for the "quality" patch on m2e-dev mailing list.  https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414If it is not too complex to get its hands in m2e code and Eclipse stuff, I would be glad to help provide "quality" patch. My idea is to have a constructive behaviour, not to trash someone else's work. I have checked out the code and managed to import all Maven projects. If you can provide me a few pointers on where to look in the code (and possibly, if you have one in your hand, a good documentation link), I should be able to work on that. Waiting for your input to continue on this subject...
m2e development environment setup is documented in . LifecycleMappingFactory.getProjectMetadataSources is the code you need to extend to read mapping metadata in workspace project .settings folder. Lifecycle mapping UI will need to be able to display effective lifecycle mapping metadata for the project and let the user change the mapping. You will need to provide at least one automated test that verifies that m2e reads expected lifecycle mapping metadata from .settings folder and that this metadata takes preference over mapping metadata from pom.xml. If you have any further questions, please reply to m2e-dev mailing list only.  http://wiki.eclipse.org/M2E_Development_Environment -- Regards, Igor
Back to the top