Actually, since this commit, https://github.com/gwt-maven-plugin/gwt-maven-plugin/commit/8b456fedae820cfdcdc581d18900f7244cf51234 using a gwt-dev and gwt-user explicit dependency in your module should disable auto-inclusion of gwt dependencies, so the plugin should work.
On Thu, Apr 27, 2017 at 10:24 AM Thomas Broyer <[email protected]> wrote: > > > On Thursday, April 27, 2017 at 9:30:36 AM UTC+2, Ignacio Baca > Moreno-Torres wrote: >> >> Yep, should be released... but it is pretty weird that the plugin should >> be released on each GWT version, this and other important issues like >> better multi-module support was the motivation to start the new generation >> plugin by Thomas Broyer (https://github.com/tbroyer/gwt-maven-plugin). >> We'll release a new version just to match the GWT version number during >> this week. In the meantime, you may try to migrate to the new generation >> one, Thanks! >> > > Also, this should work: > https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html > > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
