Skip to end of metadata
Go to start of metadata

The different runtime models explained here are all incorporated into this maven archetype using profiles. It enables execution in Development Mode and supports both packaging for deployment to a Servlet Engine and the JBoss Application Server.

To begin with we'll create a project layout using a maven build structure, which will provide us with a bare bones project, including all dependencies, which can later on be imported in your IDE of choice.

Customize the build properties according to your needs.

The project will be created in a directory that corresponds to the provided artifactId.

In a few simple steps, you have created a build environment that can build, test, package, and launch a simple application. You can now launch GWT development mode, run integration tests with coverage reporting, and package your web application for deployment.

To launch the GWT development mode, change into the project directory (name corresponding to the provided artifactId) and type:

The example application comes with an integration test suite that exercises most of its client-side and server-side code. To run the test suite, type:

To generate a set of HTML documents under target/site/jacoco/ detailing code coverage of the most recent test run, type:

By default the archetype does package the web application for Development Mode execution. To deploy your application to JBoss AS 7, you need to execute a clean rebuild using the JBoss profile (e.g. -Pjboss7).

Importing the project into eclipse
The setup instuctions for eclipse can be found in the Errai WIKI.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 11, 2012

    I had to change the archetype version to 2.0.1-SNAPSHOT to make it work


    1. Jul 12, 2012

      Thanks. The 2.0.2-SNAPSHOTs of our archetypes were never deployed. I did that now.