[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] Using lifecycle mapping from extension as well as from plugin
|
What about just registering an additional AbstractCustomizableLifecycleMapping which is mapped to a specific packaging? That can overwrite public List<AbstractProjectConfigurator> getProjectConfigurators(IMavenProjectFacade projectFacade,
IProgressMonitor monitor) to add some custom project configurators in addition to the ones being returned by LifecycleMappingFactory.getProjectConfigurators(projectFacade).
> On 21 Oct 2016, at 16:45, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
>
> 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 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) in my extension.
>> Would that still conflict with individual plugin execution mappings defined in the plugin's lifecycle-mapping-metadata.xml?
>> That way those are quite separate, right?
>>
>> Konrad
>>
>>> On 21 Oct 2016, at 14:11, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
>>>
>>> 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@xxxxxxxxxxx
>>>> 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@xxxxxxxxxxx
>>> 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@xxxxxxxxxxx
>> 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@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users
