On 8 April 2016 at 22:40, Vladimir Sitnikov <[email protected]> wrote: > Philippe> The idea was interesting because it makes things rather simple. > > What if we take a step back and consider some kind of "JMeter Plugin Market"?
This is tangential to the subject at hand. > For instance: > 1) Search & install plugins from within JMeter UI -1; that would add unnecessary classes to memory. However it could be stand-alone. Though I'm not sure how much work it would save compared with the effort of creating and maintaining it. That sounds like a good 3rd party project; it seems OT for JMeter. > 2) If loading a test plan that references not yet installed plugins, > JMeter would be able to suggest installing the required ones JMeter only knows what classes the test plan cannot find. Who is going to maintain the database of plugin locations and their classes? Who is going to vet the plugins? However it might be possible to improve the error messages that are produced when test classes cannot be found. > Vladimir
