Re: [m2e-dev] lifecycle-mapping-metadata.xml for a plugin goal that is n

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

There is no documentation of lifecycle mapping file format, but it is
generated from modello model [1], which should provide information about
all supported elements. If you have more specific questions, we'll try
to answer them here.

As name suggests, lifecycle mapping only applies for plugins bound to
project lifecycle. What you are looking for is some sort of generic
extension point that will be invoked during project import and
configuration update but I am not sure how to implement this efficiently.

Also note that currently m2e blocks projects generated by
maven-eclipse-plugin (or at least it should). We did that because we
were getting many bugreports who generated .project/.classpath/etc using
maven-eclipse-plugin and then expected m2e to dynamically manage
dependencies and other aspects of project configuration. You'll have to
convince us your solution works reliably before we lift this restriction.

[1] 
http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.core/mdo/lifecycle-mapping-metadata-model.xml?id=releases/1.0/1.0.0.20110607-2117

--
Regards,
Igor

On 11-08-31 10:36 AM, Phil Webb wrote:
> I wonder if anyone can provide some advice when working with the new
> lifecycle-mapping-metadata.xml configuration file that is part of m2e
> 1.0.
>
> 1) Is the format of this file documented anywhere, or is there any
> particular part of the codebase that describes the format?
>
> 2) Is it possible to setup a pluginExecution for a goal that is not
> bound to a lifecycle.  Specifically I am trying to write a plugin that
> will support settings such as additionalProjectnatures defined in the
> maven-eclipse-plugin configuration
> (http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html).
>   Since this plugin is usually executed manually on the command line,
> and not run as part of the the regular build, defining a
> pluginExecutionFilter against the maven-eclipse-plugin does not seem
> to work.
>
> Any advice would be gratefully received.
>
> Cheers,
> Phil.
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev