Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom component developers need own resource bundle #1390

Closed
asfimport opened this issue Jun 16, 2004 · 4 comments
Closed

Custom component developers need own resource bundle #1390

asfimport opened this issue Jun 16, 2004 · 4 comments

Comments

@asfimport
Copy link
Collaborator

Mike Stover (Bug 29603):
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.

Version: Nightly
OS: other

@asfimport
Copy link
Collaborator Author

Sebb (migrated from Bugzilla):
Gui components can override "getStaticLabel()" to retrieve the message from a private resources file.

@asfimport
Copy link
Collaborator Author

@pmouawad (migrated from Bugzilla):
This bug has been marked as a duplicate of #2642

@asfimport
Copy link
Collaborator Author

Sebb (migrated from Bugzilla):
This is not the same as #2642, which is about upgrade.properties, not message.properties

@asfimport
Copy link
Collaborator Author

@pmouawad (migrated from Bugzilla):
Not really needed knowing all plugins that currently exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant