How can I run a GWT app from gwt-maven-plugin without any browser plugins?

Question

For a GWT application which I build with the GWT Maven Plugin (gwt-maven-plugin), I can run the GWT Development environment with

mvn compile war:exploded gwt:run

and then launch a browser. This requires that the browser provides the GWT Developer Plugin. (Firefox 6 for example does not yet support the GWT Plugin).

Does the GWT Maven Plugin also allow to simply run the included Jetty container with the GWT application, without a development mode?

score 9 · Accepted Answer · answered Sep 01 '11 at 13:38

9

After configuring gwt-maven plugin you could simply run the following.

mvn jetty:run-war

After gwt compilation the resulting war will be placed in jetty and started via Maven Jetty Plugin.

answered Sep 01 '11 at 13:38

Dmitry Buzdin

1,233
1
9
15

3

Your `pom.xml` will need a dependency on the Jetty plugin. For Java 6, this might be something like `org.mortbay.jettyjetty-maven-plugin8.1.10.v20130312`. – Hbf Apr 23 '13 at 12:32
@Hbf is right about the pom: I believe the latest plugin declaration (with correct tags like for version) is at http://www.eclipse.org/jetty/documentation/current/jetty-maven-plugin.html#running-assembled-webapp-as-war – cellepo Dec 30 '15 at 08:16
You might also have to follow this and add to your .m2/settings.xml (if on running Jetty, you get [ERROR] No plugin found for prefix 'jetty' in the current project and in the plugin groups): http://stackoverflow.com/a/27744248/1357094 – cellepo Feb 14 '16 at 01:59

score 1 · Answer 2 · edited Aug 02 '12 at 13:17

The only way to run the project without plugin is to compile it and run on a server. If you are using Netbeans just hit run. The IDE will compile and deploy project on a server. In other way just compile it with the following command (you can omit tests and reports):

mvn clean:clean resources:resources compiler:compile war:exploded resources:testResources compiler:testCompile surefire:test gwt:compile war:war

After this you 've got ready to deploy war file. To deploy it to the Glassfish there are now basically three options:

Maven GlassFish Plugin

A first option would be to use the Maven GlassFish Plugin. This plugin allows to interact with a local or remote GlassFish install and the management of Glassfish domains and component deployments from within the Maven build lifecycle.

Maven Embedded GlassFish Plugin

The second option would be to use the Maven Embedded Glassfish Plugin. As stated by its name, this plugin doesn't rely on an existing install but uses an embedded GlassFish, running in the same JVM as the plugin. This plugin is extremely nice if you want to keep your build portable (anybody can get your POM and run a build involving GlassFish without having it installed) with almost the same features as a normal GlassFish install, except clustering of course (you can use a preconfigured domain.xml if you want). See Testing with the GlassFish Maven plugin and JavaDB Embedded for an example.

Maven Cargo Plugin

The work initiated by Kohsuke Kawagushi as been finally integrated in Cargo and, starting with Cargo 1.0.1, GlassFish 3.x is now supported. Using the Maven Cargo plugin is thus a third option. This would be interesting for builds that want to interact with containers in an agnostic way. But I'm not sure Cargo allows all the flexibility of the GlassFish specific plugin(s) (e.g. deployment of JMS resources, etc).

How can I run a GWT app from gwt-maven-plugin without any browser plugins?

2 Answers2

Linked