Re: [m2e-users] Using lifecycle mapping from extension as well as from plugin

2016-10-21 Thread Konrad Windszus
What about just registering an additional AbstractCustomizableLifecycleMapping which is mapped to a specific packaging? That can overwrite public List getProjectConfigurators(IMavenProjectFacade projectFacade, IProgressMonitor monitor) to add some custom project configurators in addition to the

Re: [m2e-users] Using lifecycle mapping from extension as well as from plugin

2016-10-21 Thread Igor Fedorenko
Packaging type is used to select mojo executions, so you can have different mapping for the same mojo used in different packaging types. You still have only one mapping for each mojo. -- Regards, Igor On Fri, Oct 21, 2016, at 08:35 AM, Konrad Windszus wrote: > What about if I just register a lif

Re: [m2e-users] Using lifecycle mapping from extension as well as from plugin

2016-10-21 Thread Konrad Windszus
What about if I just register a lifecycle mapping id for packaging type (similar to https://github.com/tesla/m2eclipse-tycho/blob/master/org.sonatype.tycho.m2e/lifecycle-mapping-metadata.xml#L57

Re: [m2e-users] Using lifecycle mapping from extension as well as from plugin

2016-10-21 Thread Igor Fedorenko
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 > precedenc