[
https://issues.apache.org/jira/browse/MPLUGIN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179609#comment-16179609
]
Robert Scholte commented on MPLUGIN-325:
----------------------------------------
The wording could be improved. See
https://maven.apache.org/plugin-tools/maven-plugin-plugin/updateRegistry-mojo.html
What's actually happening if that if you specify this goal within the
execution-block, it binds itself to the install-phase if you don't specify a
phase yourself.
> Documentation incorrectly claims plugin:updateRegistry is bound to install
> phase
> --------------------------------------------------------------------------------
>
> Key: MPLUGIN-325
> URL: https://issues.apache.org/jira/browse/MPLUGIN-325
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 3.5
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Reporter: Andreas Sewe
> Priority: Minor
>
> The documentation
> [claims|https://maven.apache.org/components/plugin-tools/maven-plugin-plugin/usage.html#The_plugin:updateRegistry_Goal]
> that
> {quote}
> The plugin:updateRegistry goal is bound to the install phase of the build
> life cycle.
> {quote}
> But this seems not be be the case, as a {{mvn install}} does not execute it.
> It is not listed [here as a default plugin
> binding|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_maven-plugin_packaging]
> either.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
