Hi Marc,

My understanding is that you'd need to enter a CQ for the code you are extending. If that's just classes in the core of JMeter, that should be fine.

Since your plugin runs inside JMeter, I think it'd be up to your project to decide what level of integration / testing to perform. If you happened to know that a 3rd party plugin was required for your plugin to work, it may make sense to enter a 'workswith' CQ for that module. That said, I think it would suffice to document that your users wishing to try out the plugin should use the 'usual' JMeter (with its default plugins).

In short, I think you are following the rules without exhaustive/complicated testing.

If some of your users really needed to use a certain subset of JMeter, your project's team could respond to issues as needed.

Cheers,

Jim

On 05/30/2017 10:26 AM, Pellmann Marc (INST/ECS4) wrote:

Hi,

I wrote a JMeter plugin for the Hono project. This imports and uses/extends some classes from JMeter_core (https://mvnrepository.com/artifact/org.apache.jmeter/ApacheJMeter_core/3.2).

It is written to be used inside a typical JMeter 3.2 installation, which includes more 3rd party stuff as the pure JMeter_core. My question is now if it is enough to just give the source code from JMeter_core into the CQ process?

Or do I need to check which 3rd party dependencies/jars inside the JMeter installation are at least necessary to run the simplest variant of the JMeter plugin together with JMeter and give them also as source (which might be really complicated).

Mit freundlichen Grüßen / Best regards

*Marc Pellmann*

Bosch Software Innovations GmbH

INST/ECS4

Schöneberger Ufer 89-91

10785 Berlin

GERMANY

[email protected] <mailto:[email protected]>

Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B

Executives: Dr. Ing. Rainer Kallenbach, Michael Hahn



_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation


_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

Reply via email to