We don't support those, because they aren't our parameters, they are Surefire params.
We don't subvert them either, they still work just fine, it's just that they pertain to SUREFIRE, not GWT-Maven. If you want to skip GWT-Maven based testing support for GWTTestCase tests use the param "testSkip" in config, or - Dgoogle.webtoolkit.testSkip=true" at the command line. (And, as I said there, the reason one plugin doesn't adopt another plugins options are so that they don't shadow each other, I frequently want to skip either the GWT tests, or the Surefire tests, and not both.) On Mar 30, 11:07 am, Matt Raible <[email protected]> wrote: > On Mon, Mar 30, 2009 at 7:37 AM, Charlie Collins > <[email protected]>wrote: > > > > > > > "2. The gwt-maven:gwt and gwt-maven:debug goals have moved to phase > > "install" > > where they should have been all along. If you don't want the compile > > step or > > the test step to run, use: > > mvn -Dmaven.test.skip=true -Dgoogle.webtoolkit.compileSkip=true > > gwt-maven:gwt " > > > I have a couple of questions/issues with this. > > > 1. The gwt and debug goals have been moved into and out of the > > "install" phase several times, we last decided on the group here (if I > > recall correctly) to keep them out of that for speed of the shell. I > > know about compileSkip, but I think the STANDARD usage should be that > > the GWTCompiler is not involved in just running the shell, no? > > Anyway, maybe I don't get it, what's the advantage to having it in the > > install phase and skipping the compilation - why is that the "should > > have been" way? > > > 2. If we added support for maven.test.skip I am going to remove it. > > This is an ancient deprecated option from Maven 1 time frame. Surefire > > supports it, yes, but they recommend you don't use it. Also, we have > > our own test skip parameter testSkip (http://gwt-maven.googlecode.com/ > > svn/docs/maven-googlewebtoolkit2-plugin/test-mojo.html#testSkip) that > > should be used to skip GWT tests. We need a different option than any > > the surefire plugin supports so that we can allow finer grained > > control, e.g., run the GWT tests but NOT the surefire tests, or run > > the surefire tests but NOT the GWT tests. The options we already had > > should suffice for that. > > I don't see the harm in supporting maven.test.skip. Also, they've recently > added an additional (shorter) skipTests option. I use the following in my > pom.xml to achieve "skip all tests" for both surefire and gwt-maven. > > <testSkip>${skipTests}</testSkip> > > Matt > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
