The thing is that the embedded Jboss does not simply load the first persistence.xml in the classpath. I haven’t found out what happens exactly, but the mvn test work and can deploy the app without touching a file or skipping tests.

So I have a persistence.xml in src/main/resources with the tomcat jndi name and one in src/test/resources with the jndi name for jboss.
The first thing to do is to exclude the main persistence.xml from the main resources:
<resources>
<resource>
<directory>${basedir}/src/main/resources</directory>
<excludes>
<exclude>META-INF/persistence*</exclude>
</excludes>
</resource>
</resources>

Now the persistence.xml in the main resources got invisible and the tests pass.

To have the right persistence.xml in the final app, I use the ant plugin in the prepare-package phase:

<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>prepare-package</phase>
<configuration>
<tasks>
<copy todir="${project.build.outputDirectory}">
<fileset dir="${basedir}/src/main/resources">
<include name="META-INF" />
</fileset>
</copy>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>

I must add that I had some unexplainable “unknown entity” errors in the tests. I solved this by explicitly adding the entity classes in the test persistence.xml with <class> tags.

Hope this can help.

Second try to post the pom.xml parts:

<code>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<configuration>
<update>true</update>
<mode>both</mode>
<contextFile>src/main/resources/META-INF/context.xml</contextFile>
<username>jasper</username>
<password>tomcat</password>
</configuration>
</plugin>
<!– … –>

<pluginRepositories>
<pluginRepository>
<id>mojo.snapshots</id>
<url>http://snapshots.repository.codehaus.org/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<updatePolicy>daily</updatePolicy>
</snapshots>
</pluginRepository>
</pluginRepositories>
</code>

This is the only clear explanation that I could find of how to run SeamTests with m2 that actually works.

What I normally do to use a different configuration for testing than for the main code, is the put the a file on the same location in the src/test/resources. If you use a maven version > 2.0.8 and surefire >= 2.4.3 the test resources are loaded first in the classpath. There were some bugs in previous version of maven and surefire where the classpath was inversed.

So, I tried to put a persistence.xml in src/test/resources/META-INF/persistence.xml
But for some reason, the one under src/main/resources is used in the test phase If some one knows why my theory is not working, or knows another way to solve the difference in the JNDI names, your thoughts on this are always welcome.

I also use the maven-tomcat plugin to deploy the app. Here goes the plugin config:

org.codehaus.mojo
tomcat-maven-plugin
1.0-SNAPSHOT

true
both
src/main/resources/META-INF/context.xml
configure.this.user.in.tomcat-users.xml.with.role.manager
thepassword

With this plugin you can deploy the war on a running tomcat with mvn tomcat:deploy . I have to skip the tests due to the JNDI name problem.

To download the plugin, you can use this repository:

mojo.snapshots
http://snapshots.repository.codehaus.org/

false

daily

Enjoy

I think you have missed this dependency, without which the war is having deploy time issues.

javax.xml.stream
stax-api
1.0-2

Thanks
Venki

sudo yum -y install mysql-query-browser mysql-administrator