You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/10 05:27:10 UTC

[jira] [Closed] (OOZIE-254) GH-346: add support for a test.properties file to load test system properties

     [ https://issues.apache.org/jira/browse/OOZIE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik closed OOZIE-254.
----------------------------------

    Resolution: Fixed

> GH-346: add support for a test.properties file to load test system properties
> -----------------------------------------------------------------------------
>
>                 Key: OOZIE-254
>                 URL: https://issues.apache.org/jira/browse/OOZIE-254
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> running testcases often requires specifying real unix users/groups, kerberos principals, JT/NN URI.
> running the testcases in different configurations requires different sets of system properties.
> Being able to use a test properties file to specify these system properties sets would be very convenient.
> Being able to specify different test properties files would make also easier to test different setups without having to specify a long list of of system properties in maven command line.
> By default, is a 'test.properties' file exists, its values would be loaded as system properties before running any of the testcases.
> If Maven is invoked with the option '-Doozie.test.properties=FILE' an alternate properties file would be used to load the system properties for the testcases run. This would allow having different test properties sets, for example: minicluster, simple & kerberos.
> Values specified as options to Maven in the command line override would override values in the test.properties file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira