[ 
https://jira.codehaus.org/browse/MGWT-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281540#comment-281540
 ] 

Ryan Moore commented on MGWT-311:
---------------------------------

I was able to get around this be creating the maven project with the 
webAppCreator from Google.  It would be nice though if the archetype would work 
instead of having to create it and then import it.

> GWT 2.3 + Maven 2 + maven GWT plugin 2.3 archetype not importing well into 
> Eclipse
> ----------------------------------------------------------------------------------
>
>                 Key: MGWT-311
>                 URL: https://jira.codehaus.org/browse/MGWT-311
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3.0-1
>         Environment: Windows 7/Ubuntu 11, Eclipse 3.7, GWT eclipse plugin 
> 2.3, maven 2.2.1
>            Reporter: Ryan Moore
>
> When following the instructions 
> (http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html) on 
> creating a maven + gwt project that is imported into eclipse the default 
> archetype is creating errors.  Eclipse reports 3 errors related to the POM 
> that is generated:
> *Plugin execution not covered by lifecycle configuration: 
> org.apache.maven.plugins:maven-war-plugin:2.1.1:exploded (execution: default, 
> phase: compile)
> *Plugin execution not covered by lifecycle configuration: 
> org.codehaus.mojo:gwt-maven-plugin:2.3.0-1:generateAsync (execution: default, 
> phase: generate-sources)
> *Plugin execution not covered by lifecycle configuration: 
> org.codehaus.mojo:gwt-maven-plugin:2.3.0-1:i18n (execution: default, phase: 
> generate-sources)
> Additionally on the webpage, mentioned above, it displays an image of the 
> maven plugin configuration where it is asking what goals to run on import.  
> In the latest maven version, from the eclipse market place, it is not there 
> which is misleading.
> When I try to run the application to test to see if the code works from 
> within eclipse it fails to find a module to run, but when I run "mvn gwt:run" 
> from the command line everything works fine.
> I have not modified any of the configurations beyond issuing the mvn 
> gwt:eclipse from within eclipse after the maven project has been imported 
> into eclipse.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to