On 2/26/07, Bernt M. Johnsen <[EMAIL PROTECTED]> wrote:
In the old test harness with the old tests this was impossible due to hardcoded use of port numbers (1527 etc). Is this taken into consideration when tests are moved to JUnit so that the port number(s) may be parameterized in a convenient way?
TestConfiguration sets the port to 1527, but should it? If it didn't set a port, it would still default to 1527, and then you could override the port by setting -Dderby.drda.portNumber=whatever on the command-line when invoking the junit test. andrew
