[
https://issues.apache.org/jira/browse/DERBY-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711294#action_12711294
]
Tiago R. Espinha commented on DERBY-4217:
-----------------------------------------
I have an idea. If I'm right, most of our tests extend from the
BaseJDBCTestCase and then ultimately from BaseTestCase (pretty much all should
extend from BaseTestCase?). So what if the BaseTestCase class (or the
BaseJDBCTestCase) had a port property that would be initialized with either
1527 or the port sent through the property, if any? This would of course
require going through all the tests and make sure that the port was then being
used on the test decorators, but it might be the cleaniest alternative to using
the DEFAULT_PORT property in TestConfiguration.
Regarding the alternative port, I believe that currently that's calculated with
Port+1. Unless the user defines 65535 for a port, then I see no setback in
keeping this method.
> 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: 10.6.0.0
> 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.
