[ https://issues.apache.org/jira/browse/SUREFIRE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801812#comment-17801812 ]
ASF GitHub Bot commented on SUREFIRE-2161: ------------------------------------------ michael-o opened a new pull request, #708: URL: https://github.com/apache/maven-surefire/pull/708 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/SUREFIRE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `SUREFIRE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean install` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean install`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). > Align Mojo class names and output names > --------------------------------------- > > Key: SUREFIRE-2161 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2161 > Project: Maven Surefire > Issue Type: Task > Components: Maven Surefire Report Plugin > Affects Versions: 3.0.0 > Reporter: Michael Osipov > Assignee: Michael Osipov > Priority: Major > Fix For: Backlog > > > Currently, names in those mojos are inconsistent with the rest of our > reports, namely, the output name does not have an explicit {{-report}} > suffix, the goal name should match the class name. Other plugins have been > aligned long time ago, it is about time for this one: > || Mojo class name || output name || > | -{{FailsafeReportMojo}}- \\ {{FailsafeOnlyReport}} || -{{failsafe-report}}- > \\ {{failsafe}} | > | -{{SurefireReportMojo}}- \\ {{SurefireReport}} || -{{surefire-report}}- \\ > {{surefire}} | > | -{{SurefireReportOnlyMojo}}- \\ {{SurefireOnlyReport}} || > -{{surefire-report}}- \\ {{surefire}} | -- This message was sent by Atlassian Jira (v8.20.10#820010)