Using Findbugs 2.8 plugin with the new findbugsXML.xml format produces reports
that show internal findbugs strings instead of their descriptions.

A sample of and incomplete message is:

File: CheckerSequenceFixture.java, Type:
UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR, : Low, Category: CORRECTNESS

TEST: Unknown warning UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR in
gov.epa.eis.fitnesse.checker.CheckerSequenceFixture.checker; core bug patterns
not found

A warning was recorded, but findbugs can't find the description of this bug
pattern and so can't describe it. This should occur only in cases of a bug in
FindBugs or its configuration, or perhaps if an analysis was generated using a
plugin, but that plugin is not currently loaded.

A warning was recorded, but findbugs can't find the description of this bug
pattern and so can't describe it. This should occur only in cases of a bug in
FindBugs or its configuration, or perhaps if an analysis was generated using a
plugin, but that plugin is not currently loaded.

—

Reverting to and using the old findbugs.xml format, this same report shows:

File: CheckerSequenceFixture.java, Type:
UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR, : Low, Category: STYLE

UwF: CheckerSequenceFixture.checker not initialized in constructor

This field is never initialized within any constructor, and is therefore could
be null after the object is constructed. This could be a either an error or a
questionable design, since it means a null pointer exception will be generated
if that field is dereferenced before being initialized.