auke-/gwt-maven-plugin

Starting fresh on building GWT projects with Maven

gwt-maven-plugin

This plugin aims at making it easier to build GWT projects with Maven, by providing two specific packagings: gwt-lib and gwt-app.

Basic usage

1. Add the plugin to your POM and enable extensions:

   <plugin>
     <groupId>net.ltgt.gwt.maven</groupId>
     <artifactId>gwt-maven-plugin</artifactId>
     <version>…</version>
     <extensions>true</extensions>
   </plugin>

2. configure your module name in the plugin:

   <configuration>
     <moduleName>com.example.app.App</moduleName>
   </configuration>

3. set your <packaging> to either gwt-lib or gwt-app

Features

• Adds all source roots are resources so they're packaged within the generated JAR.

• Uses src/main/super for super-sources and possibly relocate them within your module's package with <relocateSuperSource>true</relocateSuperSource>.

• Generates <inherits> from Maven dependencies: the gwt:generate-module searches for META-INF/gwt/mainModule files in the projects direct dependencies and merges them with an optional src/main/module.gwt.xml file.

  The META-INF/gwt/mainModule files are generated by the gwt:generate-module-metadata goal.

• Imports sources dependencies: dependences with a <type>java-source</type> are unpacked and added as resources. When building a GWT adapter for a shared library, this allows the library sources to be packaged within the GWT adapter lib, along with the GWT-specific sources, super-sources and GWT module.

• Packaging gwt-app generates a WAR that can be directly used as overlays in a downstream module with a war packaging.

Documentation

More docs to come, for the time being, use:

• mvn gwt:help for help on each goal
• lookup the lifecycles in the components.xml
• look at the integration tests, particularly gwt-lib, gwt-app, import-sources and e2e.