[
https://jira.codehaus.org/browse/SUREFIRE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-770.
---------------------------------
Resolution: Not A Bug
Fix Version/s: (was: Backlog)
Not related to Maven. We must not hack ClassLoader principles.
Related for J2EE frameworks.
If persistence.xml is loaded via [src/main/java].class.getClassLoader(), we
must not load another resource from src/test/resources.
In my notices, the IsolatedClassLoader should be customzable in surefire 3.0.
> persistence.xml in src/test/resources/META-INF is not taken into account
> ------------------------------------------------------------------------
>
> Key: SUREFIRE-770
> URL: https://jira.codehaus.org/browse/SUREFIRE-770
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.9
> Environment: Windows XP
> Reporter: Wolfgang Grossinger
> Labels: proposedWontFix
>
> When i have a persistence.xml in /src/main/resources/META-INF and in
> /src/test/resources/META-INF the xml for the test is never used. I found a
> few issues how to fix this but nobody had an explanation why this behavior is
> as it is. For me this behavior is really strange (and I couldn't believe that
> this is not my fault and is really not working). It seem this has to do with
> classloading - in my opinion, the test classes and the test resources should
> have priority, otherwise the whole separation of main/test is useless. I
> hope, that there is no real reason why this is so at the moment, because this
> behavior is really strange and absolutely against what the normal user would
> expect.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
