• :sparkles: Update Surefire to v3 (https://github.com/tbroyer/gwt-maven-plugin/commit/8eda8a6c1292ecad984f8b3709fe26f142020759)
• :bug: Silence "plugin validation issues" warning with Maven 3.9+, due to Maven dependencies being incorrectly declared as compile rather than provided dependencies (#160, https://github.com/tbroyer/gwt-maven-plugin/commit/a8232cbb2dd3339b21eafdd1ce6a9c0b9093a37a)

This version targets JDK 8, whereas previous versions targeted JDK 7, but given that some dependencies already required JDK 8, this is not regarded as a breaking change, hence the 1.1.0 version rather than a 2.0.0 here.

:bug: Fix gwt:generate-module for relocated artifacts (#150, 41a3c76eab5e616446ea10af5b5dca1280975846)

:tada:

• JDK 11 support
• gwt:codeserver and gwt:devmode now support <style>
• gwt:devmode now has <failOnError>
• gwt:compile, gwt:codeserver, and gwt:devmode can make use of Maven Toolchains when forking the JVM. For gwt:test, this is supported as well through Surefire.

• Updated Surefire for JDK 10 support
• Marked gwt:compile as thread-safe

• fixes a regression where gwt:codeserver and gwt:devmode no longer added dependencies with scope runtime to the classpath
• updates and cleans up dependencies

• fixes a small regression in the staleness check (for gwt:compile), introduced in the 1.0-rc-7 reworked handling of sources, where changes to non-java files in source roots would not trigger a recompilation (https://github.com/tbroyer/gwt-maven-plugin/commit/0507e6d628c4484e62952b6ce67217ae9c32e605)
• add ability to disable generation of <inherits/> from META-INF/gwt/mainModule files from dependencies to gwt:generateModule (https://github.com/tbroyer/gwt-maven-plugin/commit/bdf9864f1df52fa164c832c37350964130ef8f70)
• improves resolution of sources from projects from the reactor build for gwt:codeserver and gwt:devmode: snapshot versions weren't properly matched if snapshots were being installed/deployed, and dependencies that are missing a <type>gwt-lib</type> are now logged more prominently (see discussions in #86 and #90, again a side-effect of the reworked handling of sources in 1.0-rc-7)

• Rework handling of sources (to be included in the gwt-lib and in GWT classpath): delete the import-sources/import-test-sources goals and instead explicitly add source roots to the classpath when running GWT (using the same logic for ignoring source roots that are also declared as resources directories), and introduce a new gwt:package-lib goal (replacing jar:jar in the gwt-lib lifecycle) to package them in the JAR, without copying them to target/classes.
• localWorkers now accepts values as multipliers of the number of CPU cores, similar to mvn -T and Surefire's forkCount: e.g. 2 will use 2 workers, 0.5C will use as many workers as half the number of CPU cores.
• Remove default values from most GWT configuration properties: logLevel, failOnError, optimize, style, and localWorkers; only breaking change should be with localWorkers, previous behavior can be brought back using <localWorkers>1C</localWorkers>.
• annotation processing was actually only fixed for gwt-app, now fixed for gwt-lib as well.
• update Surefire to 2.20; this has an impact on gwt:test.

• Run import-sources/import-test-sources after compilation to take into account the output of annotation processing
• Document project layout, and layout of generated artifacts

• gwt:compile no longer include compile source roots in the classpath (they've been copied through gwt:import-sources and resources:resources anyway)
• gwt:devmode and gwt:codeserver's projects and modules discovery (when no value has been specific) has been relaxed
• gwt:test's devMode has been removed, as its default value will be switched in GWT 2.8 and it'll be deprecated

Adds classpathScope property to gwt:codeserver and gwt:codeserver to make the dependency scope configurable (defaults to runtime); and a few small fixes and documentation enhancements.