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

cbeams edited comment on SUREFIRE-459 at 9/3/08 1:27 PM:
--------------------------------------------------------------

It appears that I've just reproduced this bug against 2.4.3.  I've tried the 
'useSystemClassLoader=false' workaround, and it exposes a different problem.  
Unfortunately this issue is 'closed' and so cannot be re-opened.  Shall I 
create a new issue?

At any rate, here are the repro steps:

1) Check out, build and test Spring JavaConfig's petclinic sample:

svn co -r 789 
https://src.springframework.org/svn/spring-javaconfig/trunk/samples/org.springframework.config.java.samples.petclinic
 petclinic
cd petclinic
mvn clean test


2) Notice that there are two test failures:

Tests in error: 
  testIndex(test.web.InContainerTests)
  testFindOwners(test.web.InContainerTests)


The cause of both these issues is the following:

Error 500 /WEB-INF/jsp/includes.jsp(1,70) PWC6188: The absolute uri: 
http://www.springframework.org/tags cannot be resolved in either web.xml or the 
jar files deployed with this application

As mentioned above, downgrading to 2.3 does work - the tests pass once I do 
this.  (See revision 790 of the above to confirm).

      was (Author: cbeams):
    It appears that I've just reproduced this bug against 2.4.3.  I've tried 
the 'useSystemClassLoader=false' workaround, and it exposes a different 
problem.  Unfortunately this issue is 'closed' and so cannot be re-opened.  
Shall I create a new issue?

At any rate, here are the repro steps:

1) Check out, build and test Spring JavaConfig's petclinic sample:

svn co -r 789 
https://src.springframework.org/svn/spring-javaconfig/trunk/samples/org.springframework.config.java.samples.petclinic
 petclinic
cd petclinic
mvn clean test


2) Notice that there are two test failures:

Tests in error: 
  testIndex(test.web.InContainerTests)
  testFindOwners(test.web.InContainerTests)


The cause of both these issues is the following:

Error 500 /WEB-INF/jsp/includes.jsp(1,70) PWC6188: The absolute uri: 
http://www.springframework.org/tags cannot be resolved in either web.xml or the 
jar files deployed with this application

As mentioned above, downgrading to 2.3 does work - the tests pass once I do 
this.  (See revision 780 of the above to confirm).
  
> 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.4.3
>
>
> 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

        

Reply via email to