You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a report is generated, it will show a summary of all of the found spotbugs issues. Each spotbugs issue provides a link to the spotbugs pattern description site. This works fine if the pattern comes from the core set of spotbugs patterns. But when the bug comes from another plugin, such as fb-contrib, then the link is fairly useless.
I propose embedding the relevant descriptions to the pattern to the report itself and then linking to those descriptions.
It appears that a spotbugsXml.xml file with all of the relevant descriptions is generated anyway when I build a project, so this (or the mechanism that creates this document) could possibly be leveraged to generate the report.
The text was updated successfully, but these errors were encountered:
When a report is generated, it will show a summary of all of the found spotbugs issues. Each spotbugs issue provides a link to the spotbugs pattern description site. This works fine if the pattern comes from the core set of spotbugs patterns. But when the bug comes from another plugin, such as fb-contrib, then the link is fairly useless.
I propose embedding the relevant descriptions to the pattern to the report itself and then linking to those descriptions.
It appears that a spotbugsXml.xml file with all of the relevant descriptions is generated anyway when I build a project, so this (or the mechanism that creates this document) could possibly be leveraged to generate the report.
The text was updated successfully, but these errors were encountered: