Re: Mojo's Maven Plugin for GWT - general questions

The new plugin is called GWT Eclipse Plugin. The full explanation here https://www.youtube.com/watch?v=x04sufQce-Y. If you are starting a new project it's strongly recommended that you use the new maven plugin (https://github.com/tbroyer/gwt-maven-plugin). I think that it is much easier if you upload your project to github, so we can run it locally or comment directly on the source code.

Start from scratch is a good idea, but get inspired by https://github.com/tbroyer/gwt-maven-archetypes and https://github.com/tbroyer/gwt-maven-plugin/tree/master/src/it. IMO first try to compile, run and package the project using just maven. When this works, try to make it work in eclipse. BUT, hehe I personally thinks that this is not necessary, if you are comfortable debugging in chrome, makes no sense to use anything else than the gwt:codeserver goal. We use project configuration based on modular-webapp tbroyer archetype, and we use always the maven goals. We use the tomcat goal for the server and the gwt:codeserver for the client. You can run the goal using eclipse, and if you debug the tomcat goal you actually debug tomcat. The obvious advantage, this works everywhere and exactly the same way, command line, ci, eclipse or intellij.

So for example, this client only project https://github.com/ibaca/rxcanvas-gwt/blob/master/pom.xml should be imported correctly in eclipse (actually any ide supporting maven). But instead of using the eclipse gwt runner, use the gwt:devmode goal. :) this is my personal approach, probably not the recommended one (if such thing exists), but this is a pretty simple, easy to share and non-ide dependant strategy, so try it, if you get used to it this actually simplify your project configuration.

On Thu, Mar 2, 2017 at 6:11 PM Jens <jens.nehlmeier@gmail.com> wrote:

But calling "GWT Development mode" results in this message:

Usage: at least one module must be supplied

I don't understand this message, because I provided a name for a module when I created the project.

Sounds like Eclipse / the GWT plugin can not find your *.gwt.xml files of your project. Could it be that your source folder is not correctly detected/configured in the Eclipse project? Or  because you are using some Maven archetype the *.gwt.xml files live in /PROJECT_NAME/src/main/resources but that folder isn't marked as source root in your project build path settings?

After you have fixed the source folder issue it should work. You should already have a GWT run configuration after choosing on of the entries in the context menu you have shown in your previous mail. If you configure it and open the GWT section you will see that you have no available modules, which causes the error you are seeing.

-- J.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.