[
https://jira.codehaus.org/browse/MSQL-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282562#comment-282562
]
Robert Scholte commented on MSQL-78:
------------------------------------
The option to fork would indeed be an improvement and would solve other issues
as well.
> Maven-sql-plugin - adding option to running in different JVM
> ------------------------------------------------------------
>
> Key: MSQL-78
> URL: https://jira.codehaus.org/browse/MSQL-78
> Project: Maven 2.x SQL Plugin
> Issue Type: Improvement
> Reporter: Arul Prasad
>
> I was using the maven-sql-plugin version 1.5 and we are using the derby
> emmedded database.
> Before the test runs maven-sql-plugin executed the sql but not able to
> shutdown the derby as the maven-sql-plugin runs in the main maven
> process(this jvm is active)
> so if i launch the test using sure-fire-plugin it is running in a different
> JVM and as it is emmedded database it is not allowing to start the database
> from the different JVM
> and it leads to Error -> Caused by: ERROR XSDB6: Another instance of Derby
> may have already booted
> it is possible to execute the maven-sql-plugin in differnt JVM ? so that when
> the execution completes it will shutdwon the derby emmedded databse correctly.
>
--
This message is automatically generated by JIRA.
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
