Not possible. You need to fully define mapping in your m2e extension. -- Regards, Igor
On Fri, Oct 21, 2016, at 07:54 AM, Konrad Windszus wrote: > If a lifecycle mapping for the same plugin is contributed by both an > m2e extension as well as the plugin itself the extension will take > precedence > (http://dev.eclipse.org/mhonarc/lists/m2e-users/msg05446.html). > But what about the use case where an extension just wants to configure > an additional project configurator for the same packaging or some > goals. Is it somehow possible that both lifecycle mappings get merged? > How do I need to devise the lifecycle-mapping.xml in my extension > so that it does not interfere with actions being provided by the > plugin itself? > Thanks, > Konrad > > _________________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > To change your delivery options, retrieve your password, or > unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
