Gwt Helper Maven Plugin

This plugin contain a goal to recursively include external GWT sources to compilation classpath

License

License

Categories

Categories

Maven Build Tools GWT (Google Web Toolkit) User Interface Web Frameworks
GroupId

GroupId

io.github.gitgabrio
ArtifactId

ArtifactId

gwt-helper-maven-plugin
Last Version

Last Version

1.2
Release Date

Release Date

Type

Type

maven-plugin
Description

Description

Gwt Helper Maven Plugin
This plugin contain a goal to recursively include external GWT sources to compilation classpath
Project URL

Project URL

https://gitgabrio.github.io/gwt-helper-maven-plugin/
Source Code Management

Source Code Management

https://github.com/gitgabrio/gwt-helper-maven-plugin/tree/master

Download gwt-helper-maven-plugin

How to add to project

<plugin>
    <groupId>io.github.gitgabrio</groupId>
    <artifactId>gwt-helper-maven-plugin</artifactId>
    <version>1.2</version>
</plugin>

Dependencies

compile (2)

Group / Artifact Type Version
org.apache.maven : maven-core jar 3.6.0
org.apache.maven : maven-plugin-api jar 3.6.0

provided (1)

Group / Artifact Type Version
org.apache.maven.plugin-tools : maven-plugin-annotations jar 3.6.0

Project Modules

There are no modules declared in this project.

GWT Helper Maven Plugin

Scope of this plugin is to include arbitrary directories (in whatever location of local filesystem) to the runtime sources of a GWT project, so that GWT' Super Dev Mode will listen for changes also in those sources, eventually recompiling them when they change.

The main difference with the maven-dependency addSources goal is that this plugin recursively scan a given directory to find GWT modules, eventually filtering them based on includes/excludes patterns (optional).

GWT modules are individuated if the directory contains a src/main/resources/()/().gwt.xml file.

includes/excludes patterns are simple contains evaluation on the (full) gwt.xml file name; i.e. they are matched if that name contains those pattern, case-sensitive.

includes/excludes are mutually exclusive! If provide both, the plugin will throw an exception.

Moreover, it requires a single parameter to define the folder to scan, so that these parameter may be included as property in private user settings, to allow different configuration on different machine.

There are three configuration parameters:

  1. rootDirectories (required): comma-separated list of absolute/relative paths of directory to scan
  2. includes (optional): comma-separated list of pattern to include the module
  3. excludes (optional): comma-separated list of pattern to exclude the module

Here's an example of a valid configuration:

<plugin>
      <groupId>io.github.gitgabrio</groupId>
      <artifactId>gwt-helper-maven-plugin</artifactId>
      <version>1.2</version>
      <executions>
      <execution>
      <id>add-source</id>
      <phase>generate-sources</phase>
      <goals>
        <goal>add-source</goal>
      </goals>
      <configuration>
        <excludes>API,Mock</excludes> <!-- will exclude all GWT module whose configuration file name contains API or Mock -->
        <rootDirectories>../common-screens,/home/user/Developing/git/parent-big/external-widgets</rootDirectories> <!-- will search inside those two directories -->
      </configuration>
      </execution>
      </executions>
    </plugin>

You may download jar here

Versions

Version
1.2
1.1