https://bz.apache.org/bugzilla/show_bug.cgi?id=65116
Felix Schumacher <felix.schumac...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
Status|NEW |NEEDINFO
--- Comment #1 from Felix Schumacher <felix.schumac...@internetallee.de> ---
This issue addresses a two points simultaneously.
a) It is about merging functionality from external plug-ins into JMeter
b) It is about the way JMeter handles non-existing functions
On a)
Plug-ins are invented to ease the burden on the core JMeter team. We are only a
few people and are happy, that others can and do provide extensions via
plug-ins. Inclusion of such functionality should be done after careful
inspection (best via devs mailing list).
On b)
I think, that this can't be changed easily. The way JMeter currently works, is
that it tries to find a function by the name inside the ${...} constructs.
JMeter doesn't know or care, where the function was defined (plug-in or
built-in). So, we can't tell a user function X should be provided by plug-in Y.
At the moment the best we could do, would be to display a warning, that a
function was not found.
For such a warning, we would have to decide, where to display it - log message
or display a dialog?
Maybe we could discuss better ways to hint at the source of messages on the
mailing list (devs?).
I think it might be nice to have an option to include custom functions (as
JSR-223 snippets?) inside test plans, but on a first glance, this doesn't look
easy.
--
You are receiving this mail because:
You are the assignee for the bug.
