Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52477

XML Parsers should use report encoding given in XML file

XMLWordPrintable

    • 5.0.0 (analysis-model and warnings-ng)

      Currently, the encoding needs to defined for the parser as parameter, it would be handy if the parser could detect the encoding.

      <?xml version="1.0" encoding="UTF-8"?>
<checkstyle version="4.1">
...
</checkstyle>

          [JENKINS-52477] XML Parsers should use report encoding given in XML file

          Ulli Hafner created issue -
          Ulli Hafner made changes -
          Rank New: Ranked higher
          Ulli Hafner made changes -
          Link New: This issue is related to JENKINS-52990 [ JENKINS-52990 ]
          Ulli Hafner made changes -
          Link Original: This issue is related to JENKINS-52990 [ JENKINS-52990 ]
          Ulli Hafner made changes -
          Link New: This issue is related to JENKINS-52551 [ JENKINS-52551 ]
          Ulli Hafner made changes -
          Link Original: This issue is related to JENKINS-52551 [ JENKINS-52551 ]
          Ulli Hafner made changes -
          Component/s New: warnings-ng-plugin [ 24526 ]
          Component/s Original: warnings-plugin [ 15513 ]
          Ulli Hafner made changes -
          Component/s New: analysis-model [ 23523 ]
          Ulli Hafner made changes -
          Labels New: newbie-friendly

          Stefan Schletterer added a comment - - edited

          I second that, especially for larger C/C++ projects it is difficult to specify an encoding since most newer .cpp / .h files are UTF-8 but older .c Files in the same project are ANSI encoded (We use cppCheck and ClangTidy). The current workaround is to convert all files to UTF-8 just before the analysis.

          Stefan Schletterer added a comment - - edited I second that, especially for larger C/C++ projects it is difficult to specify an encoding since most newer .cpp / .h files are UTF-8 but older .c Files in the same project are ANSI encoded (We use cppCheck and ClangTidy). The current workaround is to convert all files to UTF-8 just before the analysis.

            mschmidae Michael Schmid
            drulli Ulli Hafner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: