[
https://issues.apache.org/jira/browse/DERBY-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-6078:
--------------------------------------
Fix Version/s: 10.9.2.2
I merged the fix to 10.9 and committed revision 1486816.
I plan to use it to pass the derby.tests.basePort property to the Jenkins build
jobs to prevent port conflicts, as discussed in this thread:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/201305.mbox/%3C51A4333E.7040801%40oracle.com%3E
> 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: 10.10.1.1
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.9.2.2, 10.10.1.1
>
> Attachments: derby-6078-1a-cmdline_property_passing.diff
>
>
> 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
