|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
If I change the value of "Default Language" to "en" instead of "en-US" then the SQL exception disappears. It seems that, although the description for this field mentions "Internally, this uses Locale.setDefault()...", one should not think that this accepts the same input as Locale.setDefault(), but only an ISO 639 two-letter language code as documented e.g. in http://www.loc.gov/standards/iso639-2/englangn.html.
Verified that it also works with "de" and "ro" as "Default Language" (the workaround using an ISO639 code solves the problem for me at least).