|
||||||||
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.
Thanks Mark - yes I assumed it was tiny mistake. Given enough users we see all bugs like that
if it is likely to happen again - could a reflection based test look for the occurrence of appropriately named resources along with the classes? (if it is unlikely to happen again, don't bother).