db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-6078) Propagate a set of properties to the junit tasks in build.xml
Date Tue, 19 Feb 2013 20:31:12 GMT
Kristian Waagan created DERBY-6078:

             Summary: Propagate a set of properties to the junit tasks in build.xml
                 Key: DERBY-6078
                 URL: https://issues.apache.org/jira/browse/DERBY-6078
             Project: Derby
          Issue Type: Improvement
          Components: Test
    Affects Versions:
            Reporter: Kristian Waagan

At times it would be very helpful to be able to specify a set of properties to pass on to
the JUnit tests when invoking the JUnit tasks in build.xml. Examples are specifying a non-default
port to use, to shorten down the run-time of the stress-test,or to specify the location of
old release jars (this is already handled explicitly).

There are several alternatives on how to do this - see http://ant.apache.org/manual/Types/propertyset.html
for details.
I suggest we try out the simplest approach first: pass on any system properties set on the
command line. It should be very simple to implement. The downside is that a property you specify
for the higher-level build script may interfer or be in conflict with the running of the tests.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message