Lifecycle mapping approach implemented in m2e 0.12 and early is not coming back, unless somebody comes up with a workable approach to make it work. This has not happened so far.
There is tentative plan for m2e 1.1 to let maven plugin developers to provide build lifecycle mapping metadata [1]. [1] http://wiki.eclipse.org/M2E_compatible_maven_plugins -- Regards, Igor On 11-10-21 10:38 AM, Staub, Edward wrote:
I was winding up a multi-month evaluation of Maven when Indigo came out. I was on the fence about adopting Maven; Indigo pushed me off the fence – to giving up on Maven. Even in my limited usage, I had to write two one-page Maven plugins that deal with code/resource generation, and use another (freemarkerpp-maven-plugin) that appears to be inactive. I have zero experience with writing Eclipse plugins. Is there any progress toward a simpler alternative mechanism for connectors, or simply allowing opt-out for Helios-style behavior? If not, I’ll just write up my Maven (non)recommendation and be done with it. I’ve been delaying in hopes that m2eclipse community pressure would lead to a change in direction. Thanks, -Ed Staub
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
