Plugin developers internationalize a plugin by modifying the Java files and the Jelly files in the plugin. They can significantly improve the translation ...
Jenkins' i18n support has some aspects that developers need to be aware of. Generation of type-safe Messages classes from Messages.properties. Marking messages ...
Missing: /url | Show results with:/url
Documentation is an important part of any Jenkins plugin. It includes user documentation (plugin pages, changelogs, user guidelines, etc.) ...
Missing: i18n- | Show results with:i18n-
In property files all non-ASCII characters need to be converted into hexcode. Modern IDEs do it automatically, so you can be just writing localizations in the ...
Jenkins supports internationalizing messages in Jelly views. In Jenkins, you add a .properties file with the .jelly file in the same directory. Any changes of .
Extensions Index. Jenkins defines extension points, which are interfaces or abstract classes that model an aspect of its behavior. Those interfaces define ...
Missing: /url | Show results with:/url
Your plugin source code will be hosted in a repository in the jenkinsci GitHub organization. You will have admin access to this repository.
Missing: i18n- | Show results with:i18n-
This allows you to read the Jenkins core source code as you develop plugins. (Or just select Download Sources on the Dependencies node.) You are advised to ...
Missing: i18n- | Show results with:i18n-
Internationalizing Messages in Java Source Code · Internationalizing Messages in Jelly Views · Internationalizing Messages in Groovy Views · Advanced Localization.
Missing: /url | Show results with:/url
This guide aims to provide guidance for project maintainers, how to prepare and setup their project, in order to use crowdin.jenkins.io.
Missing: i18n- | Show results with:i18n-