> > This would certainly be the physically simplest option, if it works. > Depends on whether code looking for locale variants checks the > `UberClassLoader`, or the defining loader of some plugin. > In the worst case, it is possible to use localization overrides via an engine similar to the Translation Assistance plugin. https://github.com/jenkinsci/translation-plugin/blob/master/src/main/java/hudson/plugins/translation/L10nDecorator.java
> That said, I expect more problems from granting commit access to plugin > repos to merge localization changes, no matter how well intentioned and > executed, while we consider plugins as largely independent subprojects. > +1, On Monday, August 20, 2018 at 5:27:29 PM UTC+2, Jesse Glick wrote: > > On Mon, Aug 20, 2018 at 9:24 AM Daniel Beck <[email protected] > <javascript:>> wrote: > > Neither Messages nor Jelly view resources work. Only 'help files' work. > > OK. Probably relatively easy to fix. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b5fad2ae-d600-439a-b502-56663a4fcf60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
