I don't think the order has any bearing on it. And in fact earlier I did run gwt:gwt first after I created the archetype, just to make sure that worked, and THEN imported. But, that said, I will check it again to make sure.
As for running it from within Eclipse, I don't do that and am not really sure what you are talking about. That probably depends on what Eclipse plugin you are using for that. Eclipse by itself doesn't have a "Maven run as." Maybe you are using Mevenide or something? I use GWT-Maven in combination with Eclipse all the time, and have for quite a long time, but I don't typically try to launch maven goals from Eclipse (I just use Eclipse to change the code, then hit reload on the shell - which I launch initially from the command line). I also use Eclipse to debug, and for that I use the gwt:debug goal (for example: http://www.screaming-penguin.com/node/7353). On Sep 18, 4:41 pm, Ginny <[EMAIL PROTECTED]> wrote: > I tried your procedure for creating the archetype, running the mvn > eclipse goal, and importing the project into eclipse and it imported > without error. The only difference from what I was doing before, is > that earlier, I was creating the archetype, running the mvn gwt goal, > and then running the mvn eclipse goal, and importing into eclipse. I > just verified that if I run the mvn gwt goal (mvn gwt:gwt) before > running mvn eclipse:eclipse and trying to import into eclipse, the > import fails as before. > > Either way, running the mvn gwt target from within eclipse (i.e. "Run > as Maven build..." and specify "gwt:gwt") fails with the same error > message as in my first message. Running mvn gwt:gwt outside of Eclipse > (i.e. from the command line) runs fine. > > Running my own run configuration from within Eclipse (i.e. not using > maven), produces the errors (in the GWT Development Shell): > Finding entry point classes > Unable to find type 'com.hit.client.Application' > ... > Failure to load module 'com.hit.Application' > > Ginny > > On Sep 18, 2:13 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > I get no errors when I import the project into Eclipse. > > > I am using Ganymede (3.4) and GWT-Maven 2.0-beta23. > > > I generated the project with the archetype: > > mvn archetype:create -DarchetypeGroupId=com.totsp.gwt - > > DarchetypeArtifactId=maven-googlewebtoolkit2-archetype - > > DarchetypeVersion=1.0 -DgroupId=myGroupId -DartifactId=myArtifactId > > > And then I ran eclipse:eclipse: > > /data/ccollins/projects/myArtifactId$ mvn eclipse:eclipse > > . . . . . > > [INFO] BUILD SUCCESSFUL > > > Then I went into Eclipse and imported existing project, and bam, it > > works. I checked all the eclipse paths and such and they look fine. > > Something else must be going on in your situation, will need more > > info. > > > Also, are you getting that error when you import the project into > > Eclipse, as you state, or when you run some type of Maven goal from > > Eclipse (which is totally different). Getting a Maven error while > > importing into Eclipse really makes no sense? > > > On Sep 18, 1:51 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > > I will add an issue to the tracker to look into Eclipse integration. > > > I haven't tested/tried that from the archetype, so I don't know > > > exactly what's up, but will look into it. > > > > On Sep 18, 11:56 am, Ginny <[EMAIL PROTECTED]> wrote: > > > > > I'm creating a new gwt project using the archetype from gwt- > > > > maven.googlecode.com. I run the command "mvn gwt:gwt" from the command > > > > line and it works. I create an eclipse project using "mvn > > > > eclipse:eclipse" and get the enclosed error when I try to import it > > > > into eclipse. I also can't run the project in eclipse (eclipse can't > > > > locate the entry point class file). Any idea what's going wrong? > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > > > construct one or more initial build plans. Reason: > > > > > No lifecycle phase binding can be found for goal: gwt, > > > > specified as a part of the execution: defaultin plugin: > > > > com.totsp.gwt:maven-googlewebtoolkit2-plugin > > > > > This plugin was resolved successfully. > > > > However, the mojo metadata it contains does not specify a default > > > > lifecycle phase binding. > > > > > Please provide a valid <phase/> specification for execution: default > > > > in plugin: com.totsp.gwt:maven-googlewebtoolkit2-plugin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
