So it looks like I may have found a bug in the plugin. I am going to post the work around I came up with in hopes that it can help others while it is resolved. The issue that is causing this problem is that the Jenkins XML parser cannot read some of the characters in the warning explanation.
Thus when you run lint I would suggest outputting it into a file such as 'lint-report-malformed.xml' then another stackoverflow question provides a Perl script for filtering invalid characters from a file. How to remove invalid characters from an xml file using sed or Perl
perl -CSDA -pe'
s/[^\x9\xA\xD\x20-\x{D7FF}\x{E000}-\x{FFFD}\x{10000}-\x{10FFFF}]+//g;
' lint-report-malformed.xml > lint-report.xml
And now the Jenkins plugin can read the file.