|
||||||||
|
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-15307) Trigger badge images... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... [email protected] (JIRA)

Tomcat 7, but as you're no doubt aware, would probably happen with any container. As a temporary workaround, I created a small webapp comprised solely of badge images and deployed it to the root context (which is testimony to how handy I think your plugin is!).
The "Green Ball" plugin had the same defect in its early days. While I doubt the fix is all that complicated, if I'm mistaken, perhaps you can use that as a reference.