Charlie, On 10 Sep., 14:53, Charlie Collins <[EMAIL PROTECTED]> wrote: > Wait, I get it now, just make it happen automatically, rather than > having to include the <goal>test</goal> in the executions thing, that > is what you are saying, right?
Exactly. When I delete the executions section from my pom to get the plugin default behaviour, the gwt plugin goals are not called at all when executing mvn compile or mvn test for example. So, the executions section seems to be mandatory. BTW, I'm using Maven 2.0.8 on Windows XP. Holger > > I believe it is already this way, but, if you configure the > <executions> at all, you are overriding the plugin defaults, and then > need to include it (if you don't want generateClientBeans and i18n so > you configure executions, etc). I will check into it more, and maybe > tweak what the default executions are, but I think test is already one > of them (yes, it should be if it isn't, agreed). > > On Sep 10, 8:34 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > gwt:test is bound to the test phase? I am not sure I understand the > > suggestion? > > > Do you mean make it run the entire test phase if gwt:test is invoked > > (meaning also fire all the prereqs and surefire itself, etc)? > > Maybe there is a way to do that, I will check into it. > > > On Sep 10, 7:52 am, Holger <[EMAIL PROTECTED]> wrote: > > > > 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 -~----------~----~----~----~------~----~------~--~---
