https://bz.apache.org/bugzilla/show_bug.cgi?id=50585
--- Comment #8 from Sebb <[email protected]> --- Note that the "search_paths property" is the standard mechanism for extending where JMeter looks when searching for functions etc. See the Javadoc for JMeterUtils.getSearchPaths() If the jars are not under lib/ext, then just update the property accordingly. I don't see why it is necessary to extend JMeter when there is already a way to solve the problem. The reason that JMeter does not search every jar in the classpath is to reduce the amount of work that is involved. Every jar has to be scanned for class names, and the ones that pass the name match are loaded in order to determine if the class implements the Function interface. The solution is to ensure that search_paths is set to the appropriate path names. -- You are receiving this mail because: You are the assignee for the bug.
