I've already removed it from the default lifecycle mapping in 3.x.
On 21-May-09, at 2:52 PM, Benjamin Bentmann wrote:
Hi,
Remove invocation of maven-plugin-plugin:updatePluginRegistry from
default lifecycle bindings
---------------------------------------------------------------------------------------------
Key: MNG-4169
URL: http://jira.codehaus.org/browse/MNG-4169
Project: Maven 2
Issue Type: Task
Components: Plugins and Lifecycle
Reporter: Benjamin Bentmann
Priority: Minor
The plugin registry will be removed from 3.x (plugin versions
should be locked down in the POM for machine-independent builds). A
user visible consequence of this is that the goal {{maven-plugin-
plugin:updatePluginRegistry}} will no longer be called
automatically for projects with packaging {{maven-plugin}}.
I would like to see how others think about properly phasing out the
plugin registry. For instance, how soon should be remove the
corresponding goal from the maven-plugin-plugin? Possibly as a
prerequiste (I haven't checked what Maven does in case a lifecycle-
induced goal is not found), how soon should we remove the lifecycle
mapping from 2.x (if at all)?.
A concrete idea could be to take the opportunity of the pending
minor update Maven 2.2 and remove the lifecycle mapping right now.
What do you think?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
the course of true love never did run smooth ...
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
