Summary: | .class overwrite / enhancement concept | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Ralf Hauser <hauser> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | michael.tschannen, p.mouawad |
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
Ralf Hauser
2008-05-15 06:53:09 UTC
JMeter will pick up all jars in lib/ext If you create your own jar, and name it so that it appears alphabetically before the JMeter jars, I think JMeter will use the classes from it in preference. Have you tried that? I just tried as you said (building a jar just for the size assertion and putting it into lib/ext), unfortunately it doesn't work. Deleting components.jar and using only a modified SizeAssertion worked without any problems. If components.jar was present, JMeter always took the standard classes (alphabetically before and after didn't work). OK. In that case, I doubt that having an override for existing classes will work. But patches / test cases welcome. In the meantime, I suggest you create a new class with the changes. P.S. Bug assignment is meant for developers when they start working on a bug. Current mechanism with JARs seems powerful enough, overriding internal classes does not seem a good idea to me. I close issue. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2112 |