[
https://issues.apache.org/jira/browse/SUREFIRE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727185#comment-17727185
]
Michael Osipov edited comment on SUREFIRE-2174 at 5/30/23 8:55 AM:
-------------------------------------------------------------------
Fixed with
[1355988759fd7edeac361b67f0b84669da4e5c54|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=1355988759fd7edeac361b67f0b84669da4e5c54]
and
[7c4faa9ae6fb6e15771753cbce7fb99fa669af41|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=7c4faa9ae6fb6e15771753cbce7fb99fa669af41].
was (Author: michael-o):
Fixed with
[1355988759fd7edeac361b67f0b84669da4e5c54|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=1355988759fd7edeac361b67f0b84669da4e5c54].
> Remove legacy Surefire test report schema file and make 3.0 default
> -------------------------------------------------------------------
>
> Key: SUREFIRE-2174
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2174
> Project: Maven Surefire
> Issue Type: Task
> Components: documentation, Maven Surefire Plugin, xml generation
> Affects Versions: 3.1.1
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.1.2
>
>
> Since 2.x is superseded with 3.0 and 3.1 is out of the door, we can remove
> the old schema and use the 3.0 one as default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
