|
||||||||
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-13892) Analysis collector marks some warnings as fixed even though they are not
ullrich.haf...@gmail.com (JIRA) Fri, 03 Aug 2012 06:31:43 -0700
- [JIRA] (JENKINS-13892) Analysis collector ... naveen.karn...@baml.com (JIRA)
- [JIRA] (JENKINS-13892) Analysis colle... naveen.karn...@baml.com (JIRA)
- [JIRA] (JENKINS-13892) Analysis colle... median...@gmail.com (JIRA)
- [JIRA] (JENKINS-13892) Analysis colle... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-13892) Analysis colle... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-13892) Analysis colle... ullrich.haf...@gmail.com (JIRA)
Nick Jones: Nick I think your case is different. Here the original warnings computation is working correctly (warnigns and findbugs). Just the aggregation is broken. In your case the warnings computation already is broken. The reason might be that the conflicting files could not be found. Can you please create a separate issue?