[
http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich closed SUREFIRE-459.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.5
Fixed in revision 642046. By default forkMode=once and
useSystemclassloader=true, which causes us to launch the tests using a a
manifest-only jar; this confuses Jetty when it uses the system property
"java.class.path" to javac to compile JSPs.
Fixed by deliberately "faking out" the java.class.path, setting it to what the
classpath would have been if we'd launched the app in a conventional way. This
also has the benefit of more generally insulating our users from the
manifest-only jar; java.class.path will look "normal" now.
In the short term, there is an easy workaround for this, which is to set
useSystemClassLoader=false. (My initial guess was correct.)
> 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
> Assignee: Dan Fabulich
> Fix For: 2.5
>
>
> 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
