https://bz.apache.org/bugzilla/show_bug.cgi?id=50585
Sebb <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO --- Comment #3 from Sebb <[email protected]> --- (In reply to bastian.dev from comment #2) > This also happens when using the JMeter API directly and providing JMeter > dependencies through the maven repositories. Can you provide a simple example script that shows the problem? > The problem is that jorphan ClassFinder#getClasspathMatches tries to find > the jars from lib/ext by jarfile the exact name in the classpath. Using > Maven artifacts results in having different names for the same modules. E.g. > ApacheJMeter_functions.jar is different than ApacheJMeter_functions-2.13.jar. > > To work around the problem you can either rename the jars in lib/ext/*.jar > to lib/ext/*-2.13.jar or patch the JMeter property "search_path" to > explicitly include the JMeter jars provided by maven (or set it to > System.getProperty("java.class.path") as a shortcut). > > It would be really helpful if you can fix the ClassFinder in JMeter to avoid > those hassles to Maven/API users. Since the user can define the "search_path" property to get round the problem, I don't see why JMeter needs to be updated. -- You are receiving this mail because: You are the assignee for the bug.
