>On 5/25/05, Dag H. Wanvik (JIRA) commented on DERBY-313:
>-------------------------------------
>Unless sombody yells, I will make a patch reflecting this finding. Yell now ;-)
>-------------------------------------
>Unless sombody yells, I will make a patch reflecting this finding. Yell now ;-)
No, you are absolutely right. My error in writing the doc.
SpecialFlags is a class in the harness, which parses the testSpecialProps property.
RunTest.java is not entirely consistent in the comments relating to this, and in 2 places it actually says testSpecialFlags. Maybe you can correct those comments in RunTest too? It should either say SpecialFlags, or testSpecialProps.
(there's on one line 1324:
' // If app props are still empty, check for any special testSpecialFlags'
and on 1332:
'// merge any special properties from testSpecialFlags')
> --------------------------------------------------
>> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
>> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
