Hi,
We discovered this week that a specific combination of maven and
surefire plugin versions produce different behaviour regarding the
class loading strategy. For example maven-2.0.7 and surefire-2.4.3 the
classpath is classes first and second test-classes. This is what
happens to you, right? If you run maven-2.0.9 and surefire-2.4.2 you
are fine.
Just turn on debugging and watch the classpath maven uses.
Regards,
On 12.09.2008, at 16:15, Ryan de Laplante wrote:
>
> This message is cross posted in nbusers mailing list. I just
> remembered
> someone telling me that this mailing list is more appropriate for
> maven
> questions.
>
> Hi,
>
> I have a maven2 project and has a persistence.xml in
> src/main/resources/META-INF/ and src/test/resources/META-INF/.
> I've got a
> dependency on TopLink JPA provider configured. When I execute the
> test it
> uses the persistence.xml from main instead of test folder. When I
> rename
> the main persistence.xml (leaving the test one named properly), then
> no
> persistence.xml is found.
>
> Any idea what is happening?
>
> FYI Spring 2.5.5 is the JPA container. It is trying to initialize a
> PU to
> inject it into an entityManagerFactory bean.
>
>
> Thanks,
> Ryan
>
> --
> View this message in context:
http://www.nabble.com/Maven2-test-not-finding-src-resources-META-INF-persistence.xml-tp19456760p19456760.html> Sent from the mevenide - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
