If your plugin is complimentary to m2e-tycho, you can define it as
"secondary". This isn't well-documented feature and may not work for
your specific usecase, but this is the only way to have two
configurators for the same plugin goal.
--
Regards,
Igor
On Thu, Nov 10, 2016, at 12:24 PM, Konrad Windszus wrote:
I want to bind my own Eclipse plugin to the same goal as m2eclipse-tycho
(https://github.com/tesla/m2eclipse-tycho) namely
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<versionRange>[1.0.0,)</versionRange>
<goals>
<goal>manifest</goal>
<goal>bundle</goal>
</goals>
</pluginExecution>
</pluginExecutionFilter>
Whenever I run Eclipse with both plugins (mine and m2eclipse-tycho) it
complains about "Conflicting lifecycle mapping (plugin execution
"org.apache.felix:maven-bundle-plugin:3.0.1:bundle (execution:
default-bundle, phase: package)"). To enable full functionality, remove
the conflicting mapping and run Maven->Update Project Configuration." How
can I prioritize and in the best case execute all configurators from the
different Eclipse Plugins?
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