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
Specifying the same XML report output multiple times seems to consistently generate a non-parseable XML file on the FileStats section, given sufficiently many files analyzed.
It seems that there is some output flushing issue between two instances of the XML reporter. I assume that also applies for other reporters.
I'd expect a reporter to always generate valid data of its output format. Spotbugs should at least warn me about reporters fighting over a file (or even throw an error), especially when generating multiple reports using different options (i.e. -xml:withMessages=spotbugs.xml -xml:minimal=spotbugs.xml
The text was updated successfully, but these errors were encountered:
Vogel612
pushed a commit
to Vogel612/spotbugs
that referenced
this issue
Mar 9, 2024
…2894)
* Keep track of constructed BugReporters for TextUiCommandLine (#2047)
* Update javadoc according to PR suggestions
* Include readability suggestions
* Add test case for two different files using the same reporter
---------
Co-authored-by: Vogel612 <vogel612@gmx.net>
For reasons I don't want to get into here, I accidentally ran spotbugs with the following abridged command:
Specifying the same XML report output multiple times seems to consistently generate a non-parseable XML file on the
FileStats
section, given sufficiently many files analyzed.It seems that there is some output flushing issue between two instances of the XML reporter. I assume that also applies for other reporters.
I'd expect a reporter to always generate valid data of its output format. Spotbugs should at least warn me about reporters fighting over a file (or even throw an error), especially when generating multiple reports using different options (i.e.
-xml:withMessages=spotbugs.xml -xml:minimal=spotbugs.xml
The text was updated successfully, but these errors were encountered: