Maven Project Build Lifecycle Mapping Problems

[Warren Tang]

Trying to import an existing maven project generated by gwt-maven-plugin 2.3.0-1 into Eclipse 3.7 (Indigo, Java EE), I got three Maven Project Build Lifecycle Mapping Problems:

Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-war-plugin:2.1.1:exploded (execution: default, phase: compile) pom.xml

Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:gwt-maven-plugin:2.3.0-1:generateAsync (execution: default, phase: generate-sources) pom.xml

Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:gwt-maven-plugin:2.3.0-1:i18n (execution: default, phase: generate-sources) pom.xml

The m2e and Maven Integration for WTP plugin are from http://download.jboss.org/jbosstools/updates/m2eclipse-wtp as recommended by gwt wiki WorkingWithMaven.

I've also read this page "M2E plugin execution not covered", which gives me three options:

• Configurator mapping. But it requires the m2e extensions (connectors?), which I guess do not exist yet. And I don't think I can develop them.
  
• Ignore. Is it safe to ignore them? I think at least two of them all related to code generation.
  
• The third option requires me know what I'm doing. I'm afraid not.
  

So what should I do?

[Jeff Larsen]

I just ignore them and that usually seems to work. 

I also get rid of all the generation of code by the gwt-maven-plugin. 

[Warren Tang]

I ignore them but my project breaks. Besides, I don't find "maven package" command in "Run As" menu. 

Till now I don't think m2e or gwt-maven-plugin is mature enough to be used. Having spent more than two days on it fixing this and fixing that, in the end I fount it to be a disappointment. 

[Warren Tang]

And I noticed the message of this group is "Hello, gwt maven plugin hackers place !!!"

But I don't want to be a hacker. I simply wanted to save time.

[David Chandler]

Hi Warren,

You can run "mvn package" on the command line or right-click on the project > Maven > Run as > Maven build.

The plugin execution failures you're seeing can be resolved by adding lifecycle mapping metadata as in the sample POMs. They are only needed for Indigo. You should not get these errors in Helios or when running mvn package from the command line.

HTH,

/dmc

On Mon, Sep 12, 2011 at 9:27 PM, Warren Tang <warren...@gmail.com> wrote:

And I noticed the message of this group is "Hello, gwt maven plugin hackers place !!!"

But I don't want to be a hacker. I simply wanted to save time.

--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/codehaus-mojo-gwt-maven-plugin-users/-/kDY42cimPxMJ.

To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.

--
David Chandler
Developer Programs Engineer, GWT+GAE
w: http://code.google.com/

b: http://turbomanage.wordpress.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools

[Andreas Horst]

I agree with Warren.

My2c:

Moving to Indigo with m2e feels more than strange! Not only you have to add lifecycle mappings polluting your POM also some of the most basic Maven build menu entries are suddenly missing. For what reason? I think I understand the intention behind the lifecycle mappings regarding broken project setups requiring you to re-enable Maven dependency management in order to resolve Eclipse's project configuration, this really was a pain sometimes prior to Indigo.

Now it is even strange that you no longer "Enable Maven Dependency Management" but convert your project into a Maven project via "Configuration", I really had to search for that. Also both menu entries "Update Project Configuration" and "Update Dependencies" open the same wizard and seem to do nothing in case m2e was confused because of missing lifecycle mappings.

Long story short: I'd stick to pre-Indigo until some of these unclear design decisions are revised.

2011/9/13 David Chandler <drfib...@google.com>

[Warren Tang]

>>Long story short: I'd stick to pre-Indigo until some of these unclear design decisions are revised.

Agreed. I've just switched back to eclipse 3.6 and e2eclipse 0.12.