How do you get jmeter to look at additional jar files outside of the lib/ext folder? Ideally I would be able to hold the jar files separately with the project the extended classes intend to help test, that way my ext folder does not become cluttered with multiple projects worth of class extentions.
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
回答1:
In user.properties you can use those properties:
- search_paths
- user.classpath
- plugin_dependency_paths
search_paths:
List of paths (separated by ;) to search for additional JMeter plugin classes,
for example new GUI elements and samplers.
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.
The given value is in addition to any jars found in the lib/ext directory.
Do not use this for utility or plugin dependency jars.
user.classpath:
List of paths that JMeter will search for utility and plugin dependency classes.
Use your platform path separator 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.
The given value is in addition to any jars found in the lib directory.
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
plugin_dependency_paths:
List of paths (separated by ;) that JMeter will search for utility
and plugin dependency classes.
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.
The given value is in addition to any jars found in the lib directory
or given by the user.classpath property.
All entries will be added to the path of the JMeter internal loader only.
For plugin dependencies using plugin_dependency_paths should be preferred over
user.classpath.