[
http://jira.codehaus.org/browse/MOJO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109897
]
Dain Sundstrom commented on MOJO-619:
-------------------------------------
This fix has been in for over 6 months now.. can we get a release?
> Allow shutting down embedded derby from sql-maven-plugin
> --------------------------------------------------------
>
> Key: MOJO-619
> URL: http://jira.codehaus.org/browse/MOJO-619
> Project: Mojo
> Issue Type: Wish
> Components: sql
> Reporter: Ivan S. Dubrov
> Assignee: Dan Tran
>
> Currently you cannot shutdown Derby (using the JDBC URL like
> "jdbc:derby:${project.build.directory}/db;shutdown=true"), because
> getConnection in this case always throws exception (the explanation of this
> behavior is here:
> http://blog.gmane.org/gmane.comp.apache.db.derby.user/month=20060701).
> I propose adding some option (like
> "<onConnectionError>skip</onConnectionError>") to ignore database connection
> errors and simply to return from the mojo without raising an exception.
> This functionality could be quite handy, since in some cases you need to
> shutdown database after executing some statements against it, just to make
> sure all subsequent connections to this embedded Derby database will be OK.
> For example, I use sql-maven-plugin to populate the database before running
> integration tests against an application deployed into the embedded Jetty
> container. And since this container runs in the same JVM, the application
> throws exception during the database startup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
