[ https://issues.apache.org/jira/browse/MCHECKSTYLE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835958#comment-16835958 ]
richard commented on MCHECKSTYLE-342: ------------------------------------- [~eolivelli] it is still valid as far as I can tell. checkstyle cannot upgraded XML version because of this. SeeĀ [https://github.com/sonatype/plexus-utils/blob/5ba6cfcca911200b5b9d2b313bb939e6d7cbbac6/src/main/java/org/codehaus/plexus/util/xml/pull/MXParser.java#L2662] which you are using to parse the XML at [https://github.com/apache/maven-checkstyle-plugin/blob/6abad1cb750244899c6e3b45a7a8bb49fba954db/src/main/java/org/apache/maven/plugins/checkstyle/CheckstyleViolationCheckMojo.java#L592] . > Support XML 1.1 > --------------- > > Key: MCHECKSTYLE-342 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-342 > Project: Maven Checkstyle Plugin > Issue Type: New Feature > Components: checkstyle:check > Affects Versions: 2.17 > Reporter: richard > Priority: Major > > Checkstyle wishes to upgrade our XML logger to print out XML 1.1 documents. > We need this functionality to support escaping non-printable characters as > XML 1.0 doesn't allow this and considers it an invalid document. > > Exception in thread "main" javax.xml.stream.XMLStreamException: ParseError > > at [row,col]:[45615,80] > > Message: An invalid XML character (Unicode: 0x2) was found in the value of > > attribute "message" and element is "error". > Checkstyle cannot upgrade until maven-checkstyle does as we use it in alot of > regression testing. If we try to give the plugin an XML 1.1 document, it > fails with the following error: > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) > > on project postgresql: Unable to read Checkstyle results xml: > > /pipeline/source/pgjdbc/pgjdbc/target/checkstyle-result.xml: only 1.0 is > > supported as <?xml version not '1.1' (position: START_DOCUMENT seen <?xml > > version="1.1"... @1:19) -> [Help 1] -- This message was sent by Atlassian JIRA (v7.6.3#76005)