Charlie, your tip does the trick, thanks. Maybe it makes sense to bind gwt:test to the test phase automatically without having to add it as an execution manually. The surefire plugin works this way, too, so it should be possible?
Holger On 9 Sep., 18:52, Charlie Collins <[EMAIL PROTECTED]> wrote: > Make sure the "test" goal is in your configuration setup for the > plugin. > > <executions> > <execution> > <goals> > <goal>mergewebxml</goal> > <goal>i18n</goal> > <goal>gwt</goal> > <goal>compile</ > goal> > <goal>test</goal> > </goals> > </execution> > </executions> > > If you have "test" in there, the GWT-Maven tests will run at the same > time, during the test phase, as the surefire ones. > > On Sep 9, 11:53 am, Holger <[EMAIL PROTECTED]> wrote: > > > I'm testing the latest version of the gwt-maven plugin. > > I am able to execute my GWT testcases by executing the goal gwt:test > > explicitly. > > When I execute "mvn test" only the surefire plugin runs but gwt:test > > does not execute. > > Is this behaviour intentional or buggy? > > > I want to execute my unit tests *and* the GWT tests with "mvn test". > > Is there a workaround to achieve this? > > > Thanks, > > Holger --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
