Hello, (It seems that accidentally I sent my first message privately, so I include it below.)
"mvn gwt-maven:gwt" does the same as "mvn com.totsp.gwt:maven- googlewebtoolkit2-plugin:2.0-RC1:gwt". Both are performing a full maven install goal (including gwt compilation, running tests, building war, etc.). Maybe my configuration is incorrect? (Although it worked well with beta26...) Thanks! Regards: Norbi -------------------------- Re: GWT-Maven 2.0-RC1 (potential last release here) Mon, 6 Apr 2009 07:56:04 -0400 Charlie Collins <charlie.coll...@gmail.com> The prefix is now "gwt-maven" and not "gwt" so as to avoid conflicts with the Codehaus plugin (which is what you are getting there). Change to "gwt-maven:gwt" and not gwt:gwt. On Mon, Apr 6, 2009 at 6:36 AM, snorbi <sandor.norb...@erinors.com> wrote: > Hello, > > I used beta26 for a long time, but I wanted to upgrade to rc1 because > of the "skipping gwt compilation" feature (and rc looks better in the > build file than beta, so I agree with the others to release a final > version ;). > > Everything seems to work ok, except starting of the gwt shell. In > beta26 I used the Eclipse Maven plugin to start the shell, using a > Maven launch configuration to invoke the goal: gwt:gwt > In case of rc1 this does not work, I get the message: > > [INFO] Searching repository for plugin with prefix: 'gwt'. > [INFO] Attempting to resolve a version for plugin: > org.codehaus.mojo:gwt-maven-plugin using meta-version: LATEST > [INFO] Attempting to resolve a version for plugin: > org.codehaus.mojo:gwt-maven-plugin using meta-version: RELEASE > [ERROR] > > Maven encountered an error while loading a plugin for use in your > build. > > Plugin: > Group-Id: org.codehaus.mojo > Artifact-Id: gwt-maven-plugin > Version: null > Referenced mojo: gwt > brought in via: null > > I get the same error when using the command line: mvn gwt:gwt (which > worked in beta26 as well). > I see that it tries to start a codehaus plugin because no group id is > specified, so I tried to use the long form > > mvn com.totsp.gwt:maven-googlewebtoolkit2-plugin:2.0-RC1:gwt > > in which case the shell is started, but only after a full Maven > install goal (which includes java compilation, gwt compilation, war > building, unit test running, etc). > > What should I use to simply start the gwt shell without invoking any > build lifecycle steps (most importantly the heavy-weight steps)? > > Thanks for your help in advance! > Regards: > Norbi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to gwt-maven@googlegroups.com To unsubscribe from this group, send email to gwt-maven+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
