|
||||||||
|
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-14461) Warnings plug... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)
- [JIRA] (JENKINS-14461) Warnings... [email protected] (JIRA)

I updated to 4.11 (the latest at http://updates.jenkins-ci.org/download/plugins/warnings/ ) and am still having the same issue.
The start of the stack trace (not sure if the rest is useful?):