Monday, March 19, 2018

Re: GWT with App Engine (standard) and maven?

As I test I just created a blank test project from the archetype.
I did not manage to run it either using "maven gwt:devmode".
Is there some additional configuration required to tell the plugin where to find the webapp?
The server launches just fine, an ancient swing window pops up, but the index.html is not there when going to

Any ideas?

On Monday, March 19, 2018 at 1:45:06 PM UTC+1, dflorey wrote:
I've migrated one of our smaller apps.
The module.gwt.xml is generated, nice!

I'm now trying to run the gwt-app.

In the old ant / Eclipse plugin days I could just click on Run and it launched all the required stuff in the background (app engine, code server etc.) so I'm a bit lost how to start the app.
We have some static resources in the the war directory (css, html launcher page), I don't know where to put these files so that they get picked up by the webserver.
I tried by putting them into the src/main/webapp directory, but this did not make it into the target war.

I tried both gwt:devmode and gwt:codeserver, both without luck.

Am I missing something obvious?

On Sunday, March 18, 2018 at 7:42:10 PM UTC+1, dflorey wrote:
That helped a lot! Thanks!
I've removed the .m2/repository and started from scratch.
I made some progress in the meantime and learned a bit about how to setup a local repository on the way to find the right structure.

I noticed that I cannot use the IsSerializable interface in the shared module, I had to replace the interface with the Serializable interface.
Looks like IsSerializable is not part of the gwt-servlet dependency?

I started with our core library. As there is no archetype for a gwt-lib I tried to start from the webapp archetype.
Then I switched the packaging from "gwt-app" to "gwt-lib" in the client module and from "war" to "pom" in the server module.
I've also removed all the tomcat and jetty plugins and the folders with the config for the webservers as I just want to build a lib.

I'm now getting an error in Eclipse in the pom telling me that "web.xml is missing and <failOnMissingWebXml> is set to 

It seems to build just fine though.

On Monday, March 12, 2018 at 4:55:21 PM UTC+1, Thomas Broyer wrote:

On Monday, March 12, 2018 at 2:10:46 PM UTC+1, dflorey wrote:
I tried to leverage your archetypes to get the gwt part (without appengine) running as a starting point.
What I did:
I created a maven project from the archetype (using the eclipse maven wizard).
I can see a nice multi-module project client/shared/server in my workspace.
As per your suggestion I just typed "mvn package -DskipTests" in the root/parent project.
But I get the same error message as before:

[INFO] --- gwt-maven-plugin:1.0-rc-9:compile (default-compile) @ formeditor-client ---
[WARNING] Error: Could not find or load main class
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] formeditor ......................................... SUCCESS [  0.000 s]
[INFO] formeditor-shared .................................. SUCCESS [  0.926 s]
[INFO] formeditor-client .................................. FAILURE [  0.614 s]
[INFO] formeditor-server .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.002 s
[INFO] Finished at: 2018-03-12T14:09:09+01:00
[INFO] Final Memory: 35M/761M

I guess I'm missing a basic step like setting a environment variable to point to my gwt installation or something?

Check that the JAR (~/.m2/repository/com/google/gwt/gwt-dev/2.8.2/gwt-dev-2.8.2.jar) is not corrupt.
Delete ~/.m2/repository/com/google/gwt/gwt-dev/2.8.2/ and re-run a build to download it again.

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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment