right, but given it is deprecated, I don't think anyone is going to be
surprised if it is removed in 2.2.x.
On 26/05/2009, at 8:19 AM, Brian Fox wrote:
Nothing used it but there where some vestigal left overs.
2009/5/24 Brett Porter
Wasn't it already deprecated in a previous release of 2.
Nothing used it but there where some vestigal left overs.
2009/5/24 Brett Porter
> Wasn't it already deprecated in a previous release of 2.0.x anyway?
>
>
> On 22/05/2009, at 12:51 PM, John Casey wrote:
>
> Sounds good to me. If we remove it from the default lifecycle mapping,
>> people could a
Wasn't it already deprecated in a previous release of 2.0.x anyway?
On 22/05/2009, at 12:51 PM, John Casey wrote:
Sounds good to me. If we remove it from the default lifecycle
mapping, people could always add it back in...at least then they'd
definitely know if they need it. :-)
Having sai
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
---
+1
On Thu, May 21, 2009 at 10:51 PM, John Casey wrote:
> Sounds good to me. If we remove it from the default lifecycle mapping,
> people could always add it back in...at least then they'd definitely know if
> they need it. :-)
>
> Having said that, I'd be *very* surprised if anyone is actually u
Sounds good to me. If we remove it from the default lifecycle mapping,
people could always add it back in...at least then they'd definitely
know if they need it. :-)
Having said that, I'd be *very* surprised if anyone is actually using
the plugin registry...
-john
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
