Re: Plugin execution not covered by lifecycle configuration
On Mon, Oct 29, 2012 at 8:56 AM, Anne Forumer wrote: > Windows 7, Eclipse 4.2 Juno, m2e 1.2, Maven 3.0.4 > > > I imported MyBatis project from SCM:SVN. Everything else seems to have gone > well except I see the following error. A jar is not being created as a result: > > Plugin execution not covered by lifecycle configuration: > org.sonatype.plugins:jarjar-maven-plugin:1.5:jarjar (execution: > jarjar-classes, phase: compile). > > > Also, there is a warning: > > maven-enforcer-plugin (goal "enforce") is ignored by m2e > > I'd appreciate any help in resolving this issue. > > Thanks This looks like an error from m2e, you will have more luck asking on the m2e user lists. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin execution not covered by lifecycle configuration
Hi Anne, > Plugin execution not covered by lifecycle configuration Getting Maven to behave in Eclipse often requires additional configuration of lifecycle mappings. Sadly, this includes the maven-jar-plugin. Here is an example: https://github.com/scijava/scijava-common/blob/205e97d0/pom-scijava/pom.xml#L208 You can read more about the rationale for this at: http://wiki.eclipse.org/M2E_plugin_execution_not_covered HTH, Curtis On Sun, Oct 28, 2012 at 5:26 PM, Anne Forumer wrote: > Windows 7, Eclipse 4.2 Juno, m2e 1.2, Maven 3.0.4 > > > I imported MyBatis project from SCM:SVN. Everything else seems to have > gone well except I see the following error. A jar is not being created as a > result: > > Plugin execution not covered by lifecycle configuration: > org.sonatype.plugins:jarjar-maven-plugin:1.5:jarjar (execution: > jarjar-classes, phase: compile). > > > Also, there is a warning: > > maven-enforcer-plugin (goal "enforce") is ignored by m2e > > I'd appreciate any help in resolving this issue. > > Thanks >
Re: Plugin execution not covered by lifecycle configuration
Hi, >I stuck with the Plugin execution not covered by lifecycle > configuration while using flexmojos-maven-plugin and getting below warning > when doing maven build > > [WARNING] Some problems were encountered while building the effective model > for com.cccis.appraiser-management:appraiser-management:swf:2.1 > [WARNING] 'dependencies.dependency.scope' for > com.adobe.flex.framework:spark:swc must be one of [provided, compile, > runtime, test, system] but is 'theme'. @ line 80, column 11 > [WARNING] 'dependencies.dependency.scope' for > com.adobe.flex.framework:halo:swc:theme must be one of [provided, compile, > runtime, test, system] but is 'theme'. @ line 88, column 11 What don't you understand when you read that warning message? Regards Thorsten
Re: Plugin execution not covered by lifecycle configuration
I would guess that flexmojo documents the procedure of listing one of their modules as an and you haven't done so. On Tue, Jan 24, 2012 at 3:14 AM, Thorsten Heit wrote: > Hi, > >> I stuck with the Plugin execution not covered by lifecycle >> configuration while using flexmojos-maven-plugin and getting below > warning >> when doing maven build >> >> [WARNING] Some problems were encountered while building the effective > model >> for com.cccis.appraiser-management:appraiser-management:swf:2.1 >> [WARNING] 'dependencies.dependency.scope' for >> com.adobe.flex.framework:spark:swc must be one of [provided, compile, >> runtime, test, system] but is 'theme'. @ line 80, column 11 >> [WARNING] 'dependencies.dependency.scope' for >> com.adobe.flex.framework:halo:swc:theme must be one of [provided, > compile, >> runtime, test, system] but is 'theme'. @ line 88, column 11 > > What don't you understand when you read that warning message? > > > Regards > > Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin execution not covered by lifecycle configuration
You should provide a small eclipse plugin that tells m2e what to do (for example simply execute the mojo). Everyone that wants to use your mojo should install this small plugin. The reason is simple: Some mojos are not executed by m2e. For example the java-compiler mojo is ignored and the ecplise compiler is executed with corresponding values. So someone decided two years ago to create error markers for every unknown mojo execution. So that one day eclipse is aware of the most mojos and they are well integrated with eclipse. A small example: 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 Notice the build.properties to include it in the build: https://github.com/php-maven/maven-php-plugin/blob/master/ide-plugins/eclipse/tags/2.0.3/org.phpmaven.eclipse.core/build.properties And notice the lifecycle-mapping extension: https://github.com/php-maven/maven-php-plugin/blob/master/ide-plugins/eclipse/tags/2.0.3/org.phpmaven.eclipse.core/plugin.xml#L41 If you are only testing a hello world sample simply ignore this problem marker or use the quickfix. The quickfix will add a small snippet into your pom telling eclipse what to do. Or simply tell your users to use the quickfix on their projects. On Thu, Jun 14, 2012 at 4:52 PM, motes motes wrote: > I am using eclipse 3.7.1, with m2eclipse 1.0.1. I have followed this > guide to create a maven-plugin: > > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html > > In another maven project I test this plugin using: > > > > > sample.plugin > hello-maven-plugin > 1.0-SNAPSHOT > > >compile > > touch > > > > > > > > But inside eclipse I get the error: > > Plugin execution not covered by lifecycle configuration: > sample.plugin:hello-maven-plugin:1.0-SNAPSHOT:touch (execution: > default, phase: compile) > > This problem has been covered here: > > http://wiki.eclipse.org/M2E_plugin_execution_not_covered > > If I change the phase to "package" it works. But what are the > recommended practices when writing maven plugins and some steps needs > to be executed during the compile phase? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
