|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I looked into what it would take to make the labels configurable and it appears to be more complex than I thought. When the labels are rendered, it's done so when the AnnotationContainer is of type JavaProject, not TabDetail. JavaProject is constructed by BuildResult so it appears the custom label definitions would need to be defined here. Replacing the hard-coded strings in main.jelly is simple enough. The Dependency-Check Jenkins plugin which uses analysis-core, already overrides TabDetail. But by the time it's called, the text to be rendered for the tabs has already been determined.