jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: JMeter Plugins and TestElement
Date Wed, 19 Feb 2014 20:20:20 GMT
Hello,
http://jmeter.apache.org/extending/jmeter_tutorial.pdf

Regards


On Wed, Feb 19, 2014 at 8:49 PM, Michael Lück <michael@lueckonline.net>wrote:

> Thanks Philippe,
>
> that's good to hear.
>
> could you point me to some resource where i can find more about the plugin
> mechanism?
>
> Regards,
> Michael
>
> Am 18.02.2014 21:24, schrieb Philippe Mouawad:
>
>> On Mon, Feb 17, 2014 at 8:29 PM, Michael Lück <michael@lueckonline.net>
>> wrote:
>>
>>  Hi,
>>>
>>> i'm currently in a discussion with the maintainer of the the
>>> jmeter-maven-plugin whether or not the following assumptions is true for
>>> all plugins:
>>>
>>> - a jar which contains a class that implements TestElement must be a
>>> plugin
>>>
>>>  Yes but not only.
>> For example
>> *JavaSamplerClient implementations must reside in lib/ext or search_paths,
>> they are considered as plugins*
>>
>>
>>
>>  - jars which contain implementations of TestElement should always reside
>>> under lib/ext
>>>
>>>  => They can be in other paths referenced by search_paths property (see
>> user.properties file)
>> But usually they are in lib/ext.
>>
>>  Background:
>>> I'm trying to define a logic whether an jar should be copied to lib/ext
>>> or
>>> directly to lib. Currently the jar is examined for (direct or indirect)
>>> implementations of TestElement. If at least one class is found the jar is
>>> expected to be a plugin.
>>>
>>> Regards,
>>> Michael
>>>
>>>
>>>
>>>
>>
>
>


-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message