db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4217) Make the default port for the suites.All run configurable with a system property.
Date Mon, 25 May 2009 18:55:46 GMT

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

Tiago R. Espinha commented on DERBY-4217:

So to wrap it up in a nutshell. We need four ports as far as testing goes:
- derby.tests.port
- derby.tests.alternativePort
- derby.tests.replicationPort
- derby.tests.slavePort

And basically, if they aren't explicitly set, they can be defined with offsets based on a
port. This port is 1527 unless otherwise overridden with the derby.tests.port property.

My idea is to add four (static) properties to TestConfiguration and force the decorators to
use these properties [which are set to their default values or to the system properties if
they are defined]. The point of having new properties is that I need a coherent way of fetching
at least the main port from within other tests (like the ij test). I could just fetch the
property from within the other tests, but that doesn't seem a good programming practice at

> Make the default port for the suites.All run configurable with a system property.
> ---------------------------------------------------------------------------------
>                 Key: DERBY-4217
>                 URL: https://issues.apache.org/jira/browse/DERBY-4217
>             Project: Derby
>          Issue Type: Sub-task
>    Affects Versions:
>            Reporter: Tiago R. Espinha
>            Assignee: Tiago R. Espinha
>         Attachments: DERBY-4217.patch, DERBY-4217.patch, DERBY-4217.patch, DERBY-4217.patch,
DERBY-4217.stat, DERBY-4217.stat, ReproNetworkServerControl.java
> The goal is to make the port used for suites.All configurable through a system property
passed on to the JVM.

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

View raw message