maven lifecycle configuration

I'm playing with maven plugins, specifically i'm trying to develop a custom maven plugin for eclipse. All goes well, it builds from console ... etc until:`

"Plugin execution not covered by lifecycle configuration"

appears. I research and find this:

http://wiki.eclipse.org/M2E_plugin_execution_not_covered;

obviously i do not want to ignore the plugin's execution, the execute instruction does not seem to work, as for the delegate to project configurator, i am not able to find

AbstractJavaProjectConfigurator.java.

I've searched in org.eclipse.jdt , core and source but there is no reference to what i am searching, best match i could find was here:

http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.jdt/src/org/eclipse/m2e/jdt

All in one, what i want to achive is this: "Starting with m2e 1.1, maven plugin developers are able to provide lifecycle mapping metadata as part of the plugin itself." as stated in the first link i inserted. Any help would be greatly appreciated.

Answers


To simply bypass the mojo execution or telling m2e to simply execute your mojo via maven embedder you need the following:

  1. a proper lifecycle mapping as explained in your link. Reference: https://github.com/php-maven/maven-php-plugin/blob/master/ide-plugins/eclipse/tags/2.0.3/org.phpmaven.eclipse.core/lifecycle-mapping-metadata.xml However I put it in the root of the eclipse project to be able to debug it (finding those extra resources sometimes failes if you put them in src folders).

  2. A build properties to embedd it into build: https://github.com/php-maven/maven-php-plugin/blob/master/ide-plugins/eclipse/tags/2.0.3/org.phpmaven.eclipse.core/build.properties

  3. Activation via dependencies and extension:

Hope this helps. I was confused about the project configurator too. But the above example does not require any project configurator.


Need Your Help

In what order are Android objects that are defined in the manifest initialized?

manifest android-contentprovider android

I try to access my Application from a ContentProvider but it seems that it is being created after the ContentProvider, or at least it's having its onCreate() called after my provider. Which begs the