Re: Sling IDE: Lifecycle Mapping Extension Point

2016-10-11 Thread Konrad Windszus
Just for completeness: This feature of m2e was added in the context of https://bugs.eclipse.org/bugs/show_bug.cgi?id=337010 , so is actually pretty old, so we can safely rely on it. > On 11 Oct 2016, at 09:04, Konrad Windszus

Re: Sling IDE: Lifecycle Mapping Extension Point

2016-10-11 Thread Konrad Windszus
This should not be necessary. Whenever there is an unknown packaging the DefaultLifecycleMapping.java is used which derives from AbstractCustomizableLifecycleMapping as well. There is even a test explicitly written for that in

Re: Sling IDE: Lifecycle Mapping Extension Point

2016-10-10 Thread Georg Henzler
If I remember it correctly, it was needed to make the project configurator work at all. Note that ContentPackageLifecycleMapping is not just empty but extends AbstractCustomizableLifecycleMapping [1] and this code only becomes active for content packages because of the reference chain [2]. But

Sling IDE: Lifecycle Mapping Extension Point

2016-10-10 Thread Konrad Windszus
In https://github.com/apache/sling/blob/trunk/tooling/ide/eclipse-m2e-ui/lifecycle-mapping-metadata.xml#L41 we have referenced the explicit lifecycle mapping id from