[ 
https://jira.codehaus.org/browse/SUREFIRE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-508.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.11
         Assignee: Kristian Rosenvold

Since the claspath length limit has been largely eliminated, I updated the FAQ 
with the proper settings to run GWT in r1206339. The faq also contains 
reference to the codehaus plugin.

> cannot run GWTTestCases with surefire
> -------------------------------------
>
>                 Key: SUREFIRE-508
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-508
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading
>    Affects Versions: 2.4.3
>            Reporter: nicolas de loof
>            Assignee: Kristian Rosenvold
>             Fix For: 2.11
>
>
> GWTTestCase require some complex setup, as tje GWT compiler requires acces to 
> the java sources, and classpath scanning for available jars at runtime :
>       <plugin>
>         <artifactId>maven-surefire-plugin</artifactId>
>         <configuration>
>           <additionalClasspathElements>
>             
> <additionalClasspathElement>src/main/java</additionalClasspathElement>
>             
> <additionalClasspathElement>src/test/java</additionalClasspathElement>
>             
> <additionalClasspathElement>target/generated-sources/gwt</additionalClasspathElement>
>           </additionalClasspathElements>
>           <useManifestOnlyJar>false</useManifestOnlyJar>
>           <systemProperties>
>             <property>
>               <name>gwt.args</name>
>               <value>-out target/www-test</value>
>             </property>
>           </systemProperties>
>           <argLine>-Xmx256M</argLine>
>         </configuration>
>       </plugin>
> Even with this configuration, the test fails with a tomcat ClassCastException 
> "GWTShellServlet is not a Servlet"
> I may be wrong, but it seems the useManifestOnlyJar=false mode still uses the 
> tmp file classpath elements to build it's classpath, and not the system 
> classpath.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to