In the past https://github.com/tesla/m2eclipse-tycho
<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
<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
<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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users
