Lines 257-277
Link Here
|
257 |
<p>JMeter automatically finds classes from jars in the following directories:</p> |
257 |
<p>JMeter automatically finds classes from jars in the following directories:</p> |
258 |
<ul> |
258 |
<ul> |
259 |
<li>JMETER_HOME/lib - used for utility jars</li> |
259 |
<li>JMETER_HOME/lib - used for utility jars</li> |
260 |
<li>JMETER_HOME/lib/ext - used for JMeter components and add-ons</li> |
260 |
<li>JMETER_HOME/lib/ext - used for JMeter components and plugins</li> |
261 |
</ul> |
261 |
</ul> |
262 |
<p>If you have developed new JMeter components, |
262 |
<p>If you have developed new JMeter components, |
263 |
then you should jar them and copy the jar into JMeter's <b>lib/ext</b> directory. |
263 |
then you should jar them and copy the jar into JMeter's <b>lib/ext</b> directory. |
264 |
JMeter will automatically find JMeter components in any jars found here. |
264 |
JMeter will automatically find JMeter components in any jars found here. |
|
|
265 |
Do not use lib/ext for utility jars or dependency jars used by the plugins; |
266 |
it is only intended for JMeter components and plugins. |
265 |
</p> |
267 |
</p> |
266 |
<p>Support jars (libraries etc) should be placed in the <b>lib</b> directory.</p> |
268 |
<p>If you don't want to put JMeter plugin jars in the <b>lib/ext</b> directory, |
267 |
|
|
|
268 |
<p>If you don't want to put JMeter extension jars in the <b>lib/ext</b> directory, |
269 |
then define the property <b>search_paths</b> in jmeter.properties. |
269 |
then define the property <b>search_paths</b> in jmeter.properties. |
270 |
Do not use lib/ext for utility jars; it is only intended for JMeter components. |
|
|
271 |
</p> |
270 |
</p> |
|
|
271 |
<p>Utility and dependency jars (libraries etc) can be placed in the <b>lib</b> directory.</p> |
272 |
<p>If you don't want to put such jars in the <b>lib</b> directory, |
273 |
then define the property <b>user.classpath</b> or <b>plugin_dependency_paths</b> |
274 |
in jmeter.properties. See below for an explanation of the differences. |
275 |
</p> |
272 |
<p> |
276 |
<p> |
273 |
Other jars (such as JDBC, JMS implementations and any other support libaries needed by the JMeter code) |
277 |
Other jars (such as JDBC, JMS implementations and any other support libaries needed by the JMeter code) |
274 |
should be placed in the <b>lib</b> directory - not the <b>lib/ext</b> directory</p> |
278 |
should be placed in the <b>lib</b> directory - not the <b>lib/ext</b> directory, |
|
|
279 |
or added to <b>user.classpath</b>.</p> |
275 |
<p>Note: JMeter will only find .jar files, not .zip.</p> |
280 |
<p>Note: JMeter will only find .jar files, not .zip.</p> |
276 |
<p>You can also install utility Jar files in $JAVA_HOME/jre/lib/ext, or you can set the property <b>user.classpath</b> in jmeter.properties</p> |
281 |
<p>You can also install utility Jar files in $JAVA_HOME/jre/lib/ext, or you can set the property <b>user.classpath</b> in jmeter.properties</p> |
277 |
<p>Note that setting the CLASSPATH environment variable will have no effect. |
282 |
<p>Note that setting the CLASSPATH environment variable will have no effect. |
Lines 543-556
Link Here
|
543 |
You may list their classname or their class label (the string that appears |
548 |
You may list their classname or their class label (the string that appears |
544 |
in JMeter's UI) here, and they will no longer appear in the menus.</property> |
549 |
in JMeter's UI) here, and they will no longer appear in the menus.</property> |
545 |
<property name="search_paths"> |
550 |
<property name="search_paths"> |
546 |
List of paths (separated by ;) that JMeter will search for JMeter add-on classes; |
551 |
List of paths (separated by ;) that JMeter will search for JMeter plugin classes, |
547 |
for example additional samplers. |
552 |
for example additional samplers. A path item can either be a jar file or a directory. |
548 |
This is in addition to any jars found in the lib/ext directory. |
553 |
Any jar file in such a directory will be automatically included in search_paths, |
|
|
554 |
jar files in sub directories are ignored. |
555 |
The given value is in addition to any jars found in the lib/ext directory. |
549 |
</property> |
556 |
</property> |
550 |
<property name="user.classpath"> |
557 |
<property name="user.classpath"> |
551 |
List of paths that JMeter will search for utility classes. |
558 |
List of paths that JMeter will search for utility and plugin dependency classes. |
552 |
This is in addition to any jars found in the lib directory. |
559 |
Use your platform path separator to separate multiple paths. |
|
|
560 |
A path item can either be a jar file or a directory. |
561 |
Any jar file in such a directory will be automatically included in user.classpath, |
562 |
jar files in sub directories are ignored. |
563 |
The given value is in addition to any jars found in the lib directory. |
564 |
All entries will be added to the class path of the system class loader |
565 |
and also to the path of the JMeter internal loader. |
553 |
</property> |
566 |
</property> |
|
|
567 |
<property name="plugin_dependency_paths"> |
568 |
List of paths (separated by ;) that JMeter will search for utility |
569 |
and plugin dependency classes. |
570 |
A path item can either be a jar file or a directory. |
571 |
Any jar file in such a directory will be automatically included in plugin_dependency_paths, |
572 |
jar files in sub directories are ignored. |
573 |
The given value is in addition to any jars found in the lib directory |
574 |
or given by the user.classpath property. |
575 |
All entries will be added to the path of the JMeter internal loader only. |
576 |
For plugin dependencies using plugin_dependency_paths should be preferred over |
577 |
user.classpath. |
578 |
</property> |
554 |
<property name="user.properties"> |
579 |
<property name="user.properties"> |
555 |
Name of file containing additional JMeter properties. |
580 |
Name of file containing additional JMeter properties. |
556 |
These are added after the initial property file, but before the -q and -J options are processed. |
581 |
These are added after the initial property file, but before the -q and -J options are processed. |