You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2008/02/20 05:31:28 UTC

[jira] Commented: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4

    [ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124423 ] 

Dan Fabulich commented on SUREFIRE-459:
---------------------------------------

Rather than just grabbing the current latest (which might be broken for some other reason), could you give me a specific SVN URL and revision number to pull down?

Prior to knowing anything else about your failing test, I might suggest that you take a look at SUREFIRE-453 and try configuring 2.4 with useSystemClassLoader=false.

> Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
> ----------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-459
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-459
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading, plugin
>    Affects Versions: 2.4, 2.4.1
>         Environment: Maven 2.0.8, Windows XP
>            Reporter: Nils-Helge Garli
>
> We have an integration test running in a Struts 2 sample application, and after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is failing. There's an issue registered in the Struts 2 JIRA explaining the error: https://issues.apache.org/struts/browse/WW-2494
> I have no idea what's causing the error, but I suspect it has something to do witn classloader configuration, as aparently no tld files are found inside the jar files on the classpath.
> It should be pretty easy to reproduce. Just checkout the Struts 2 code and run 'mvn test' on the portlet example application.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira