[
https://jira.codehaus.org/browse/SUREFIRE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287834#comment-287834
]
Kristian Rosenvold commented on SUREFIRE-770:
---------------------------------------------
A common approach to solving this issue is to have the following dependency
chain (A->B->C) (A depends on B depends on C). In module B & C you can have the
test configuration in test scope only and not in main scope. In module A you
have the configuration in main scope only. In that way module "A" will be the
only one with the non-test configuration.
> 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
> Fix For: Backlog
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
