[
https://issues.apache.org/jira/browse/SUREFIRE-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090789#comment-15090789
]
ASF GitHub Bot commented on SUREFIRE-1216:
------------------------------------------
Github user mfriedenhagen commented on the pull request:
https://github.com/apache/maven-surefire/pull/110#issuecomment-170283705
* @Tibor17, I think I was confused by test files in the Jenkins' XUnit
plugin (see
https://github.com/jenkinsci/xunit-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/xunit/types/junit/testcase1/input.xml).
* To reproduce the Jenkins issue I just copied `input.xml` to testcase5 and
added the schema declarations.
* Now this firstly failed because of SUREFIRE-1216 and after I used
`nonamespaceschemalocation` lateron the input data was just incorrect (more
than 3 digits after the decimal separator). Sorry for the confusion. I can go
ahead and just rebase this patch into master.
> 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)
