Bug 29603 - Custom component developers need own resource bundle
Summary: Custom component developers need own resource bundle
Status: RESOLVED WONTFIX
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: Nightly (Please specify date)
Hardware: Other other
: P3 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-16 14:14 UTC by Mike Stover
Modified: 2019-02-10 21:32 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Stover 2004-06-16 14:14:38 UTC 
Anyone writing a custom jmeter component has to make resource strings.  With
TestBean, it's easy enough, but for regular gui components, their only current
option is modding the messages.properties file and recompiling JMeter.

External developers should have the option of specifying a custom resource
file/location that jmeter tries to get properties from first, and then fall back
on the given jmeter resources.  This would also allow anyone to override the
messages.
Comment 1 Sebb 2009-05-08 17:32:30 UTC 
Gui components can override "getStaticLabel()" to retrieve the message from a private resources file.
Comment 2 Philippe Mouawad 2011-11-12 15:15:01 UTC 

*** This bug has been marked as a duplicate of bug 52161 ***
Comment 3 Sebb 2011-11-14 01:16:53 UTC 
This is not the same as Bug 52161, which is about upgrade.properties, not message.properties
Comment 4 Philippe Mouawad 2019-02-10 21:32:03 UTC 
Not really needed knowing all plugins that currently exist.
Comment 5 The ASF infrastructure team 2022-09-24 20:37:33 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1390