On 29 August 2015 at 17:02, <[email protected]> wrote: > Author: pmouawad > Date: Sat Aug 29 16:02:41 2015 > New Revision: 1700056 > > URL: http://svn.apache.org/r1700056 > Log: > Fix typo and clarify one field > > Modified: > jmeter/trunk/bin/user.properties > > Modified: jmeter/trunk/bin/user.properties > URL: > http://svn.apache.org/viewvc/jmeter/trunk/bin/user.properties?rev=1700056&r1=1700055&r2=1700056&view=diff > ============================================================================== > --- jmeter/trunk/bin/user.properties (original) > +++ jmeter/trunk/bin/user.properties Sat Aug 29 16:02:41 2015 > @@ -25,11 +25,11 @@ > # Any jar file in such a directory will be automatically included, > # jar files in sub directories are ignored. > # The given value is in addition to any jars found in the lib/ext directory. > -# Do not use this for utility ir plugin dependecy jars. > +# Do not use this for utility or plugin dependency jars. > #search_paths=/app1/lib;/app2/lib
Does the separator here also depend on the platform separator? Or does JMeter parse it always with ";"? > # List of paths that JMeter will search for utility and plugin dependency > classes. > -# Use your platform path separator to separate multiple paths. > +# Use your platform path separator (java.io.File.separatorChar in Java) to > separate multiple paths. > # A path item can either be a jar file or a directory. > # Any jar file in such a directory will be automatically included, > # jar files in sub directories are ignored. > @@ -37,7 +37,10 @@ > # All entries will be added to the class path of the system class loader > # and also to the path of the JMeter internal loader. > # Paths with spaces may cause problems for the JVM > +#Example for windows (; separator) > #user.classpath=../classes;../lib;../app1/jar1.jar;../app2/jar2.jar > +#Example for linux (:separator) > +#user.classpath=../classes:../lib:../app1/jar1.jar:../app2/jar2.jar > > # List of paths (separated by ;) that JMeter will search for utility Is that correct? If so it is inconsistent with the parsing of the other properties. And it could cause a problem on OSes that use a different separator, especially if they allow ";" in path names. One such is OpenVMS which uses ";" as the file version prefix. > # and plugin dependency classes. > > In theory JMeter could always use ";" to parse the paths. However the paths would then look different from the actual ones Also, ";" might legitimately be present in a path element. So I agree that the code should use the local separator rather than assuming ";"
