Jetty daemon and useTestClasspath, what am I doing wrong? - maven

Question

Since I'm trying to set an embded container in my maven project I want to it run during the integration test phase. I have two problems with jetty that I can not manage to resolve :
<daemon>true</daemon> doesn't have the expected effect. The server is run but then it locks the build process (in fact it blocks the unit tests). So where am I supposed to place that configuration ?
The <useTestClasspath>true</useTestClasspath> is a mystery for me. I don't want to use the src/main/webapp/WEB-INF/lib to place the postgresql jar (which is called by jetty for the datasource (postegresql-driver)) because it would be embeded in the application and I don't want it to be in the war (client side). So I want to use <useTestClasspath>true</useTestClasspath> but when I place postgresql in the src/test/resources it doesn't find/recognize it. So, how am I supposed to use that property ?
Here is the complete plugin configuration :
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.9</version>
<executions>
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run-war</goal>
</goals>
<configuration>
<useTestClasspath>true</useTestClasspath>
<daemon>true</daemon>
<contextPath>agepro-prototype</contextPath>
<webApp>
${project.build.directory}/agepro-prototype.war
</webApp>
</configuration>
</execution>
<execution>
<id>stop-jetty</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
<configuration>
<connectors>
<connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>9091</port>
</connector>
</connectors>
<stopPort>9092</stopPort>
<stopKey>test</stopKey>
</configuration>
</plugin>
Thanks in advance for the help you could provide me. I must apologize for my grammar, because my english is quite bad.
Regards,
Depado

Answer 1

Not sure about your first question, but as for your second, specify the postgresql jar as provided scope in your main dependency block (this will prevent it from being bundled in the war), and add an additional dependency block in the jetty plugin definition (with compile scope), which will make the postgresql jar available at jetty runtime:
<build>
<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.9</version>
<executions>
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run-war</goal>
</goals>
<configuration>
<daemon>true</daemon>
<contextPath>agepro-prototype</contextPath>
<webApp>
${project.build.directory}/agepro-prototype.war
</webApp>
</configuration>
</execution>
<execution>
<id>stop-jetty</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
<configuration>
<connectors>
<connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>9091</port>
</connector>
</connectors>
<stopPort>9092</stopPort>
<stopKey>test</stopKey>
</configuration>
<dependencies>
<dependency>
<groupId>postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>9.1-901-1.jdbc4</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>9.1-901-1.jdbc4</version>
<scope>provided</scope>
</dependency>
</dependencies>
I don't want to use the src/main/webapp/WEB-INF/lib to place the postgresql jar (which is called by jetty for the datasource (postegresql-driver)) because it would be embeded in the application and I don't want it to be in the war (client side). So I want to use true but when I place postgresql in the src/test/resources it doesn't find/recognize it
You shouldn't be placing jars in any folders (src/main/resources or src/main/webapp/WEB-INF/classes), they should all be defined as dependencies in your pom.
I also imagine the useTestClasspath is being ignored when you define the webApp configuration element, as the it's using the packaged war, which will not contain your test resources / classes

Answer 2

useTestClasspath/useTestScope are only available for jetty:run
This is why it doesn't work with jetty:run-war and other jetty:goals