It is quite simple,
just open the run configuration, change to the "Arguments" tab and
append the full path to module definition(s) to the "Program
arguments" field, omitting the .gwt.xml extension.
On 21 Apr., 18:39, cri wrote:
> I'm trying to use gwt project generated by using the gwt-maven-pl
Update (final one I hope!):
After creating the initial project with the gwt-maven-plugin
archetype, it appears that you should not use "import... -> existing
maven projects" (which comes from m2eclipse I think). Instead, you
should use eclipse's native "import... -> existing projects into
workspac
Update:
The problem was that the launch configuration created by the gwt-maven-
plugin was missing the module specification. Once I added this, the
app did come up when invoking "Run As/Web Application".
The current problem that I'm working on is that my app compiled for
web mode isn't coming up.
Steps to create a new GWT project using Maven and GPE:
1. Create new maven project using eclipse.
2. User gwt-maven-plugin artifact while creating.
3. Now manually enable GWT (and GAE) for your project.
Now you can use google development mode and compile options as usual,
similar to
I'm trying to use gwt project generated by using the gwt-maven-plugin
archetype but don't very far. I feel I must be making a simple
mistake.
It would be great if maven support was provided directly by GWT.
Here is are the steps I followed with gwt-maven-plugin (from the gwt-
maven-plugin documen