Releases: tbroyer/gwt-maven-plugin
Releases · tbroyer/gwt-maven-plugin
1.1.0
- ✨ Update Surefire to v3 (8eda8a6)
- 🐛 Silence "plugin validation issues" warning with Maven 3.9+, due to Maven dependencies being incorrectly declared as
compile
rather thanprovided
dependencies (#160, a8232cb)
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.
1.0.1
1.0.0, at last!
🎉
- JDK 11 support
gwt:codeserver
andgwt:devmode
now support<style>
gwt:devmode
now has<failOnError>
gwt:compile
,gwt:codeserver
, andgwt:devmode
can make use of Maven Toolchains when forking the JVM. Forgwt:test
, this is supported as well through Surefire.
JDK 10 and better parallel builds support
- Updated Surefire for JDK 10 support
- Marked
gwt:compile
as thread-safe
Fix codeserver/devmode regression
- fixes a regression where
gwt:codeserver
andgwt:devmode
no longer added dependencies with scoperuntime
to the classpath - updates and cleans up dependencies
Fix staleness check regression, improves devmode/codeserver
- 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 (0507e6d) - add ability to disable generation of
<inherits/>
fromMETA-INF/gwt/mainModule
files from dependencies togwt:generateModule
(bdf9864) - improves resolution of sources from projects from the reactor build for
gwt:codeserver
andgwt: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)
Reword source handling, remove configuration properties' defaults
- Rework handling of sources (to be included in the
gwt-lib
and in GWT classpath): delete theimport-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 newgwt:package-lib
goal (replacingjar:jar
in thegwt-lib
lifecycle) to package them in the JAR, without copying them totarget/classes
. localWorkers
now accepts values as multipliers of the number of CPU cores, similar tomvn -T
and Surefire'sforkCount
: 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
, andlocalWorkers
; only breaking change should be withlocalWorkers
, previous behavior can be brought back using<localWorkers>1C</localWorkers>
. - annotation processing was actually only fixed for
gwt-app
, now fixed forgwt-lib
as well. - update Surefire to 2.20; this has an impact on
gwt:test
.
Fix annotation processing, document project layout
- 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
Fixed gwt:compile, enhancements for standalone apps
gwt:compile
no longer include compile source roots in the classpath (they've been copied throughgwt:import-sources
andresources:resources
anyway)gwt:devmode
andgwt:codeserver
'sprojects
andmodules
discovery (when no value has been specific) has been relaxedgwt:test
'sdevMode
has been removed, as its default value will be switched in GWT 2.8 and it'll be deprecated
Fixes and enhanced documentation, and addition of classpathScope property
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.