[
https://issues.apache.org/jira/browse/MPIR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074466#comment-15074466
]
Hervé Boutemy commented on MPIR-323:
------------------------------------
yes, we need to find steps to improve the situation, and define target in a
meaningful way: I updated issue description with a table and stroked values for
changes to try to clearly describe proposed changes
if we create 2 Mojos, people who use the plugin in {{reporting/plugins/plugin}}
section without configuring {{reportSets/reportSet/reports/report}}, i.e.
having "full" reports, will have changed reports twice: I don't think this is a
good idea, since lazy people will not understand (2 files is not an issue, but
2 entries in menu is an issue)
then we need to be cautious and precisely describe what "deprecating" means
here: IMHO a deprecated Mojo requires to not create its report, or it will
wreck havock on "full" reports
And we can't have any warning displayed, since we can't detect if the report
was explicitely configured or only part of "full" report
Then I don't think having duplicated Mojos improves anything: it could have
improved life for people configuring reportSets (with a warning and clean
explanation warning message on how to use the new goal), but it would be at the
price of direct users not even aware or reportSets
then IMHO, 3.0 is not about removing duplicated Mojos but about adding
introducing visible change
the invisible change, that is the Mojo class name change, can be done
independently: in 2.9 if you want
> Align Mojo, class and output names
> ----------------------------------
>
> Key: MPIR-323
> URL: https://issues.apache.org/jira/browse/MPIR-323
> Project: Maven Project Info Reports Plugin
> Issue Type: Task
> Components: cim, mailing-list, project-team
> Affects Versions: 2.7
> Reporter: Michael Osipov
> Fix For: next-major
>
>
> Currently, names in those mojos are inconsistent with the rest and moreover,
> they do not correspond to the naming in the POM reference. Let's align the
> following to resemble element names in the POM:
> || Mojo class name || goal name || [POM
> element|http://maven.apache.org/ref/current/maven-model/maven.html] || report
> file ||
> | -{{CimReport}}- \\ {{CiManagementReport}} | -{{cim}}- \\ {{ci-management}}
> | {{ciManagement}} | -{{integration.html}}- \\ {{ci-management.html}} |
> | {{MailingListsReport}} | -{{mailing-list}}- \\ {{mailing-lists}} |
> {{mailingLists}} | -{{mail-lists}}- \\ {{mailing-lists.html}} |
> | -{{TeamListReport}}- \\ {{ProjectTeamReport}} | {{project-team}} |
> {{developers}}, {{contributors}} | -{{team-list.html}}- \\
> {{project-team.html}} |
> | -{{LicenseReport}}- \\ {{LicensesReport}} | -{{license}}- \\ {{licenses}} |
> {{licenses}} | -{{license.html}}- \\ {{licenses.html}} |
> | -{{IssueTrackingReport}}- \\ {{IssueManagementReport}} |
> -{{issue-tracking}}- \\ {{issue-management}} | {{issueManagement}} |
> -{{issue-tracking.html}}- \\ {{issue-management.html}} |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
