|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16203) Jenkins tools auto inst... [email protected] (JIRA)
- [JIRA] (JENKINS-16203) Jenkins tools auto... [email protected] (JIRA)
- [JIRA] (JENKINS-16203) Jenkins tools auto... [email protected] (JIRA)
- [JIRA] (JENKINS-16203) Jenkins tools auto... [email protected] (JIRA)
- [JIRA] (JENKINS-16203) Jenkins tools auto... [email protected] (JIRA)
- [JIRA] (JENKINS-16203) Jenkins tools auto... [email protected] (JIRA)
- [JIRA] (JENKINS-16203) Jenkins tools auto... [email protected] (JIRA)

As kohsuke points out in the commit, display name is for UI and can change based on locale so it is probably a better idea to use an ID.
As I already said, readability shouldn't matter since you are not supposed to care about paths where tools are automatically installed.
You tried to solve an issue (embedding additional libs in a tool) but you didn't use the proper solution, which is to build a .zip with tool + additional libs, and to use this .zip as source of tool installation.