|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
To avoid use of IETF BCP 47 language tags as language setting for the locale plugin is a sufficient workaround for this problem.
The real problem IMHO is that a totally misleading SQL exception appears, maybe it could be fixed by introducing a more specific exception handling (e.g. catching the exception for the invalid language setting before the SQL exception can occur).