Test surefire config for GWTTestCase and if it works, can the Test mojo

[GoogleCodeExporter]

From Miles in the forum, this setup is supposed to work:

<plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-surefire-plugin</artifactId>
                                <version>2.4.3</version>
                                <configuration>
                                        <additionalClasspathElements>

<additionalClasspathElement>${project.build.sourceDirectory}</
additionalClasspathElement>

<additionalClasspathElement>${project.build.testSourceDirectory}
</additionalClasspathElement>
                                        </additionalClasspathElements>

<useSystemClassLoader>true</useSystemClassLoader>

<useManifestOnlyJar>false</useManifestOnlyJar>
                                        <forkMode>always</forkMode>
                                        <systemProperties>
                                                <property>
                                                        <name>gwt.args</name>
                                                        <value>-out
target/www</value>
                                                </property>
                                        </systemProperties>
                                        <argLine>-Xmx256m</argLine>
                                </configuration>
                        </plugin> 

Original issue reported on code.google.com by charlie....@gmail.com on 28 Nov 2008 at 10:13

[GoogleCodeExporter]

I'm not sure how this is supposed to work, how will it have the proper 
classpath for
the platform-specific GWT-shell?

I get this error in failed tests:
java.lang.NoClassDefFoundError: com/google/gwt/dev/GWTShell

Right now I can't even get the gwt-maven test goal to work (beta26?), I get the 
same
error. 

Original comment by mark.ren...@gmail.com on 6 Jan 2009 at 5:36

[GoogleCodeExporter]

This is only the special config section for SUREFIRE, and this issue relates to 
using
it rather than the built in GWT-Maven support for GWTTestCase tests.  (It gets 
the
rest of the classpath stuff from the other POM settings. I have tried a very 
similar
setup to this before and ran into other Surefire issues, but the classpath is 
not an
issue.)

If you have a separate issue with GWT-Maven please enter a new (and more 
detailed?)
issue, or try the forum?  

Original comment by charlie....@gmail.com on 6 Jan 2009 at 7:55

[GoogleCodeExporter]

Original comment by charlie....@gmail.com on 26 Jan 2009 at 11:02

• Added labels: Type-Task

[GoogleCodeExporter]

Move this issue to codehaus, same deal, if it works we DO NOT need the separate 
test
mojo.  Not doing this at GWT-Maven though, as trying to lock down major changes 
and
keep things steady (preparing to move to Codehaus Mojo for new features, 
approach
changes, such as this). 

Original comment by charlie....@gmail.com on 30 Mar 2009 at 4:00

• Changed state: WontFix