[
https://issues.apache.org/jira/browse/MNG-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949137#comment-17949137
]
Slawomir Jaranowski commented on MNG-8717:
------------------------------------------
[~cstamas]
{quote}
Yup, go for it. Still, maven binding is not used, when plugin is present, as it
carries own binding, no?
{quote}
As I know binding from plugins are used only when extension is enabled.
We should not duplicate definition in Maven core and in plugins ...
> Remove maven-plugin-plugin:addPluginArtifactMetadata from default binding
> -------------------------------------------------------------------------
>
> Key: MNG-8717
> URL: https://issues.apache.org/jira/browse/MNG-8717
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.9.10, 4.0.0-rc-4
>
>
> Goal {{maven-plugin-plugin:addPluginArtifactMetadata}} is not used for Maven
> 3.9.+
> since {{3.13.0}} version of {{maven-plugin-plugin}}
> We cen remove it from default binding.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
