On 3 November 2011 16:49, Philippe Mouawad <[email protected]> wrote: > Only useful case is when you make many tests with different JMX files and > don't want to use Keystore Config but I agree it's not a big argument :-) .
The keystore is currently enabled if the System property is defined. If the KeystoreConfig were enhanced to include the keystore file name, then we could change the code to only use the Keystore if the Config element is present. This would behave more like the CookieManager. Howerer this would be a change to existing tests that use keystores. However, we can use the KeystoreConfig as the only means to configure the indexes; if a user wants to vary the values at run time they can always use the __P() function. > Should I remove them everywhere ? > I need to think a bit more about it. > > On Thu, Nov 3, 2011 at 5:43 PM, sebb <[email protected]> wrote: > >> On 3 November 2011 16:29, <[email protected]> wrote: >> > Author: pmouawad >> > Date: Thu Nov 3 16:29:32 2011 >> > New Revision: 1197207 >> > >> > URL: http://svn.apache.org/viewvc?rev=1197207&view=rev >> > Log: >> > BUG_52033 : >> > Default to jmeter.properties if start and end not set >> > Handle errors in inputed start and endIndex >> >> I don't think we need to support the properties. >> They were introduced after 2.5.1, so have not been in a released product. >> >> Not sure using the property gains anything. >> > > > > -- > Cordialement. > Philippe Mouawad. >
