Skip to content

Migrating from Mojo GWT Maven Plugin to TBroyer

Mark Kevin Baldemor edited this page Nov 21, 2017 · 3 revisions

Reason why we migrated to TBroyer

  • Mojo tied to GWT Version, so once GWT Released another version then you need to wait also for the mojo gwt-maven-plugin to have the same released to marry the GWT.
  • TBroyer aims to have a plugin that runs independently without waiting for new releases from GWT.
  • TBroyer does not require the gwt-servlet anymore.
  • TBroyer has custom packaging called gwt-lib (Which GMD Core projects used) & gwt-app (For web application specific)
  • TBroyer Support multi-module project.
  • Other benefits from Thomas Broyer
  • Also there's a NOTICE saying that

The legacy maven plugin (Mojo) is still supported but it is strongly encouraged to use the new one (TBroyer) for new projects.

Migration Steps

  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>
  1. Configure your module name in the plugin:
  <configuration>
    <moduleName>com.example.app.App</moduleName>
    <!-- This will support still when your packaging is  war instead of gwt-app -->
    <skipModule>true</skipModule>
  </configuration>
  1. Install your project
   mvn clean install
  1. Running your project
   mvn gwt:codeserver

References

TBroyer Official Github Repo
TBroyer Official Documentation