[
https://issues.apache.org/jira/browse/MPLUGIN-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559184#comment-17559184
]
Konrad Windszus edited comment on MPLUGIN-297 at 6/27/22 2:14 PM:
------------------------------------------------------------------
bq. simply removing plugins section does not looks a good idea
That was not proposed in this ticket, the proposal was to merely remove the
{{<build>-><plugins>-><plugin>-><version>}} element, as its version is managed
(so there is no need to duplicate the version number).
was (Author: kwin):
bq. simply removing plugins section does not looks a good idea
That was not proposed in this ticket, the proposal was to merely remove the
{{<version>}} element from the plugin, as its version is managed (so there is
no need to duplicate the version number).
> plugin-info.html should contain a better Usage section
> ------------------------------------------------------
>
> Key: MPLUGIN-297
> URL: https://issues.apache.org/jira/browse/MPLUGIN-297
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
> Affects Versions: 3.4
> Reporter: Konrad Windszus
> Priority: Major
> Attachments: MPLUGIN-297-maven-plugin-tools.patch
>
>
> The usage section in the page "plugin-info.html" being generated by the
> {{report}} goal of the {{maven-plugin-plugin}} contains the version
> information of the plugin in both sections {{pluginManagement}} as well as
> {{plugins}}. I think it is best practice to only give out the version in the
> {{pluginManagement}}. Therefore please remove the version from the
> {{plugins}} section.
> One example for that can be seen in
> https://maven.apache.org/plugins/maven-compiler-plugin/plugin-info.html.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
