Re: [m2e-users] Connector as well as Integrated Lifecycle Mapping for th

[Anton Tanasenko <atg.sleepless@xxxxxxxxx>]

Hi,

M2e-tucho mapping should probably take precedence in such case.

See https://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/lifecyclemapping/LifecycleMappingFactory.java#n265

2016-03-12 13:14 GMT+02:00 Anders Hammar <anders@xxxxxxxxxx>:

As I understand the plugin has priority. The connector will be ignored.

/Anders (mobile)

On Mar 12, 2016 12:00, "Konrad Windszus" <konrad_w@xxxxxx> wrote:

In the past https://github.com/tesla/m2eclipse-tycho was used to  configure the execution of maven-bundle-plugin:manifest and goal (https://github.com/tesla/m2eclipse-tycho/blob/master/org.sonatype.tycho.m2e/lifecycle-mapping-metadata.xml#L100). Now there is a pull request which adds an integrated lifecycle mapping to the maven-bundle-plugin (https://github.com/apache/felix/pull/57). What will happen once the m-b-p will contain its own lifecycle-mapping. Will it override any mapping from external connectors or will both be executed? If the latter is the case, how can we make sure that for m-b-p only the internal one is used, but no longer the one from m2eclipse-tycho?

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

--

Regards,

Anton.