I solved this problem with a bit of trickery using Ant within Maven.
The behaviour is correct to the EJB3 spec of scoping rules for persistence.xml.
I've submitted an issue with Surefire here which goes into more detail, including the
ant hack:
http://jira.codehaus.org/browse/SUREFIRE-443
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127244#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...