Bug 59751 - GUI language settings in user.properties without effect
Summary: GUI language settings in user.properties without effect
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.0
Hardware: PC All
: P3 regression (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-24 07:52 UTC by robert.strauch+apache
Modified: 2016-09-14 20:47 UTC (History)
2 users (show)



Attachments
Screenshot showing GUI with language settings in user.properties (24.54 KB, image/png)
2016-06-24 07:52 UTC, robert.strauch+apache
Details
Screenshot showing GUI with language settings in jmeter.properties (22.29 KB, image/png)
2016-06-24 07:55 UTC, robert.strauch+apache
Details
Sample user.properties (5.41 KB, text/plain)
2016-06-24 07:55 UTC, robert.strauch+apache
Details

Note You need to log in before you can comment on or make changes to this bug.
Description robert.strauch+apache 2016-06-24 07:52:41 UTC
Created attachment 33982 [details]
Screenshot showing GUI with language settings in user.properties

DESCRIPTION

The GUI language is not changed when settings are done in user.properties. If the settings are located in jmeter.properties the GUI language is set to the configured language.

This didn't happen in JMeter 2.13. Language settings from user.properties worked properly.


STEPS TO REPRODUCE

1)
Stop JMeter.

2)
Edit user.properties in JMeter bin directory and add the following settings.

language=en
locales.add=en


3)
Start JMeter via jmeter.bat. The GUI is set to German default locale language.

4)
Move the settings to jmeter.properties and restart JMeter. The GUI is set to the configured language.
Comment 1 robert.strauch+apache 2016-06-24 07:55:18 UTC
Created attachment 33983 [details]
Screenshot showing GUI with language settings in jmeter.properties
Comment 2 robert.strauch+apache 2016-06-24 07:55:40 UTC
Created attachment 33984 [details]
Sample user.properties
Comment 3 Philippe Mouawad 2016-07-31 19:05:54 UTC
This was always like this even in 2.13 version.
It is a known issue but I see it is not documented anywhere.
Note that to change correctly language, you should also add JVM property.