On Tue, Aug 28, 2018 at 2:34 AM arch <[email protected]> wrote: > Agree with this solution. And I give a prototype plugin. > https://github.com/LinuxSuRen/localization-plugin
Nice, did you get this to work already? There are a few things to check: · core vs. plugin localization · `Messages_zh_CN.properties` (so `Messages.some_key()` Java calls) · `*_zh_CN.properties` (localization from Jelly views like `index`) · `help*_zh_CN.html` if these are even supported (I cannot remember offhand) · `mvn hpi:run` incl. live reloading after saving a resource in the source tree · effectiveness in a `$JENKINS_HOME/plugins/*.jpi` (this is a different class loading mode) > Do I need to create a ticket on JIRA or just everyone take a look at this > project? I think this would make a good JEP describing what you propose to do and making sure other localizers are ready to coöperate, since this clearly goes beyond a usual plugin HOSTING request: it would involve _removing_ localization resources from lots of existing repositories, adjusting the default plugin list in the Setup wizard, and maybe some infrastructure tasks. And there are some details that need to be settled such as the plugin code names (which cannot be changed after publishing): rather than, say, `chinese-localization` I might suggest something more regular like `localization-zh_CN`. -- 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/CANfRfr1YJ0BuDZ6mXAKO%2BUFkG0tFiun6W-9GpWSfxVyUr5%2BZPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
