[
http://jira.codehaus.org/browse/SUREFIRE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-340:
----------------------------------
Fix Version/s: 2.4
> Resource classpaths differ if project has flat structure, causing
> MappingExceptions and more.
> ---------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-340
> URL: http://jira.codehaus.org/browse/SUREFIRE-340
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Maven 2.0.6,
> IBM 1.4.2 JDK on RHEL 4 on an HP Itanium, and also Apple 1.5.0 on Mac OSX
> Reporter: Barrett Nuzum
> Fix For: 2.4
>
> Attachments: surefire-bug-testcases.tar.gz
>
>
> We have heavy dependence on Spring and Hibernate.
> We maintain a flat project structure as this is a great deal easier to manage
> in an IDE.
> We have tests that pass if you build them from a leaf-level application.
> If run from the parent project, as a multimodule build, the tests fail.
> Root
> \- Parent Build
> \- Child1 Build
> The exact same project can pass a multimodule build if the project structure
> is nested.
> Root
> \- Parent Build
> \- Child1 Build
> Both scenarios are included in the attached file.
> The child builds correctly under both scenarios if you cd directly to it's
> directory and run install or test.
> Both builds display an appropriate classpath if run with -X, but the flat
> structure cannot find the resource.
> I believe this to be an incompatibility with Spring and it's methods for
> getting a ResourceLoader.
> All permutations and combinations of:
> <useSystemClassLoader>, <childDelegation> and <forkMode>
> also have no effect.
--
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
