[
https://issues.apache.org/jira/browse/SUREFIRE-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090793#comment-15090793
]
ASF GitHub Bot commented on SUREFIRE-1216:
------------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/110#issuecomment-170285026
Feel free to push it to master. I will then update a branch 3.0-rc1.
You can then close it in jira.
If you have time we would need to alter `StatelessXmlReporter` with
surefire|failsafe xsd. Now they are same but in the future both may split. The
same as we are going to do with system properties which lack of prefix
surefire|failsafe. Additionally this xsd
https://maven.apache.org/surefire/maven-failsafe-plugin/xsd/surefire-test-report.xsd
needs to be renamed to `failsafe-test-report.xsd` which is still possible
because the class `StatelessXmlReporter` does not alter such xsd. They are both
the same, hopefully now, but may necessarily not to be same.
Thx.
> TEST-*.xml files generated by Surefire are invalid
> --------------------------------------------------
>
> Key: SUREFIRE-1216
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1216
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19.1
> Reporter: Mirko Friedenhagen
> Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> See SUREFIRE-964 as well. The XML produced is invalid because
> {{schemaLocation}} *must* include two URIs, as outlined in
> [xmlschema-1|http://www.w3.org/TR/xmlschema-1/#schema-loc].
> Because of this, the Xerces parser fails in the Jenkins XUnit plugin and e.g.
> IntelliJ is not able to parse the file correctly.
> Suggested solution is to replace {{xsi:schemaLocation}} by
> {{xsi:noNamespaceSchemaLocation}}, which fixes this for the Unit plugin as
> well the file is parseable by IntelliJ.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
