Open mkienenb opened 4 years ago
It looks to me like the html transform doesn't know how to handle errors for bug types which span multiple classes, such as NM_CONFUSING where the error is that two classes have methods that differ by capitalization.
I don't remember enough about xml transforms to fix it. I'll open a Spotbugs issue later.
I'm having issues with spotbugs ignoring my findbugs exclude files, so I want to track that down first to see what else might be affected by this after I exclude NM_CONFUSING
<BugInstance type="NM_CONFUSING" priority="3" rank="19" abbrev="Nm" category="BAD_PRACTICE">
<Class classname="com.xyz.applications.epay.cayenne._EbppDAOCayenne">
<SourceLine classname="com.xyz.applications.epay.cayenne._EbppDAOCayenne" start="62" end="858" sourcefile="_EbppDAOCayenne.java" sourcepath="com/xyz/applications/epay/cayenne/_EbppDAOCayenne.java"/>
</Class>
<Method classname="com.xyz.applications.epay.cayenne._EbppDAOCayenne" name="getACHProcessingQueueList" signature="()Ljava/util/List;" isStatic="false">
<SourceLine classname="com.xyz.applications.epay.cayenne._EbppDAOCayenne" start="67" end="67" startBytecode="0" endBytecode="48" sourcefile="_EbppDAOCayenne.java" sourcepath="com/xyz/applications/epay/cayenne/_EbppDAOCayenne.java"/>
</Method>
<Class classname="com.xyz.cayenne.ebpp.entity.generated._Account">
<SourceLine classname="com.xyz.cayenne.ebpp.entity.generated._Account" start="26" end="246" sourcefile="_Account.java" sourcepath="com/xyz/cayenne/ebpp/entity/generated/_Account.java"/>
</Class>
<Method classname="com.xyz.cayenne.ebpp.entity.generated._Account" name="getAchProcessingQueueList" signature="()Ljava/util/List;" isStatic="false">
<SourceLine classname="com.xyz.cayenne.ebpp.entity.generated._Account" start="131" end="131" startBytecode="0" endBytecode="51" sourcefile="_Account.java" sourcepath="com/xyz/cayenne/ebpp/entity/generated/_Account.java"/>
</Method>
</BugInstance>
There's already an existing spotbugs issue for the html problem, which I've updated.
So I'm testing my PR[1] port from findbugs which allowed findbugs/spotbugs to handle arbitrarily large argument lists with ant/CLI against my application. I've been using this code with findbugs for years, and it was easy to port it to spotbugs.
However. there's a couple of odd errors being returned.[2] I've verified that the same ant task running findbugs instead of spotbugs still works so it's not a bad environment.
The first error seems to be a problem with the html report. Changing it to "xml" doesn't generate the error.
The second issue is a vague error, maybe warning, that doesn't tell me what's wrong:
For what it's worth, my ant task call is here:
[1] Allow any ant task or command-line user to specify large values or many arguments #1098 https://github.com/spotbugs/spotbugs/pull/1098
[2]