db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5731) It should be possible to start ij in a mode when it terminates in case of any error
Date Sun, 29 Apr 2012 14:45:48 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264564#comment-13264564

Knut Anders Hatlen commented on DERBY-5731:

Hi Julo,

Thanks for the patch. I haven't looked at it yet, but I have one comment to the described

A system property that controls the behaviour sounds very reasonable when you start ij from
the command line and run it in a separate process. When using the programmatic API (the ij.runScript()
method), on the other hand, a system property might not work so well, as it affects the entire
JVM, and one may have multiple applications running in the same JVM expecting different behaviour
from ij. For such applications it might be better if we add a new ij command, for example
called exitonerror, modelled after the localizeddisplay and elapsedtime commands. Then the
scripts that wanted this behaviour could start by invoking "exitonerror on" without affecting
other applications running ij.runScript() in the same JVM.

If we add such a command, it probably isn't necessary to add the system property, but we might
still want to do that for convenience, I suppose. How do you think an ij command would work
for the use case you're struggling with?
> It should be possible to start ij in a mode when it terminates in case of any error
> -----------------------------------------------------------------------------------
>                 Key: DERBY-5731
>                 URL: https://issues.apache.org/jira/browse/DERBY-5731
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Julius Stroffek
>            Assignee: Julius Stroffek
>              Labels: ij
>         Attachments: derby-5731.diff
> It should be possible to determine from the exit status of ij whether the commands that
were executed failed or not. This should not be the default behavior as it will break the

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message