Including the jdbc:derby:;shutdown with the
<skipOnConnectionError>true</skipOnConnectionError> parameter in the
1.1-SNAPSHOT did the trick. Thanks for the help.
For the benefit of others, I've added the following execution:
<execution>
<id>shutdown-database-so-that-test-can-run</id>
<phase>process-test-resources</phase>
<goals>
<goal>execute</goal>
</goals>
<configuration>
<url>jdbc:derby:;shutdown=true</url>
<skipOnConnectionError>
true
</skipOnConnectionError>
</configuration>
</execution>
Thanks again.
--
View this message in context:
http://www.nabble.com/sql-maven-plugin%2C-derby%2C-and-test-cases--%3E-failed-to-start-database-tf3263205s177.html#a9081501
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
