Hardcoding locale breaks import into reportportal.

[tangentially]

junit-xml-formatter/java/src/main/java/io/cucumber/junitxmlformatter/XmlReportWriter.java

Line 22 in e2bb2c1

private final NumberFormat numberFormat = NumberFormat.getInstance(Locale.US);

Suggested fix:
private final NumberFormat numberFormat = NumberFormat.getNumberInstance();
{
numberFormat.setGroupingUsed(false);
}

Example bad string:

<testsuite errors="0" failures="0" name="io.cucumber.core.plugin.JUnitFormatter" skipped="0" tests="15" time="1,384.047">

Correct string:

<testsuite errors="0" failures="0" name="io.cucumber.core.plugin.JUnitFormatter" skipped="0" tests="15" time="1384.047">

[mpkorstanje]

Interesting, the surefire-test-report-3.0 requires the thousands separator.

junit-xml-formatter/surefire-test-report-3.0.xsd

Line 27 in e2bb2c1

<xs:pattern value="(([0-9]{0,3},)*[0-9]{3}|[0-9]{0,3})*(\.[0-9]{0,3})?"/>

But looking at the latest version that isn't the case anymore.

https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/resources/xsd/surefire-test-report.xsd

[mpkorstanje]

Looks like that changed since apache/maven-surefire@96dedb3

[mpkorstanje]

@tangentially could you verify if #83 works for you?

Currently surefire writes float values (https://www.datypic.com/sc/xsd/t-xsd_float.html) but maybe report portal is a bit more picky about the values it accepts.

[tangentially]

Thankyou, we can test once the new binaries become available. I've forwarded to my dev team to see if they can do some testing of the fix before then.