Lifecycles and Packagings

The Maven Plugin for GWT provides two lifecycles, triggered by two new packaging values: gwt-lib and gwt-app.

The gwt-lib packaging triggers a lifecycle that will build a gwt-lib artifact.

The gwt-lib lifecycle has the same phases as the default lifecycle, and resembles the jar lifecycle but with different default bindings:

Phase	Bindings
`initialize`	`gwt:enforce-encoding`, `gwt:add-super-sources`, and `gwt:add-test-super-sources`
`generate-resources`	`gwt:generate-module`, and `gwt:generate-module-metadata`
`process-resources`	`resources:resources`
`compile`	`compiler:compile`
`process-test-resources`	`resources:testResources`
`test-compile`	`compiler:testCompile`
`test`	`gwt:test`
`package`	`gwt:package-lib`
`install`	`install:install`
`deploy`	`deploy:deploy`

The gwt-app packaging triggers a lifecycle that will build a gwt-app artifact.

The gwt-app lifecycle has the same phases as the default lifecycle, and resembles the war lifecycle but with different default bindings:

Phase	Bindings
`initialize`	`gwt:enforce-encoding`, `gwt:add-super-sources`, and `gwt:add-test-super-sources`
`generate-resources`	`gwt:generate-module`
`process-resources`	`resources:resources`
`compile`	`compiler:compile`
`test-compile`	`compiler:testCompile`
`test`	`gwt:test`
`prepare-package`	`gwt:compile`
`package`	`gwt:package-app`
`install`	`install:install`
`deploy`	`deploy:deploy`