You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tiago R. Espinha (JIRA)" <ji...@apache.org> on 2009/05/14 00:20:45 UTC

[jira] Assigned: (DERBY-4223) Provide the ability to use properties with ij.runScript()

     [ https://issues.apache.org/jira/browse/DERBY-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tiago R. Espinha reassigned DERBY-4223:
---------------------------------------

    Assignee: Tiago R. Espinha

> Provide the ability to use properties with ij.runScript()
> ---------------------------------------------------------
>
>                 Key: DERBY-4223
>                 URL: https://issues.apache.org/jira/browse/DERBY-4223
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 10.6.0.0
>            Reporter: Tiago R. Espinha
>            Assignee: Tiago R. Espinha
>
> Currently, the system properties aren't being used by the runScript() method on the org.apache.derby.tools.ij
> This raises an issue with allowing the port used for the JUnit tests to be customized, therefore blocking DERBY-4217. The idea, was to allow properties such as ij.protocol to be set either as system properties, or in a Properties object, then passed to the runScript() method.
> Please share any thoughts and ideas as to which may be the best approach.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.