Re: design for transparent plugin downloading

2005-05-06 Thread Thomas Van de Velde
Thanks for this clarification. M2 really starts to look great. On 5/6/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Thomas Van de Velde wrote: > > >Brett, > > If I understand this right, you'll be able to tell Maven to > automatically > >check for an update of a particular plugin (great for a

Re: design for transparent plugin downloading

2005-05-05 Thread Brett Porter
Thomas Van de Velde wrote: >Brett, > If I understand this right, you'll be able to tell Maven to automatically >check for an update of a particular plugin (great for automatically >distributing bug fixes across projects, much like the Eclipse Update >Manager). This would be accomplished by addi

Re: design for transparent plugin downloading

2005-05-05 Thread Thomas Van de Velde
Brett, If I understand this right, you'll be able to tell Maven to automatically check for an update of a particular plugin (great for automatically distributing bug fixes across projects, much like the Eclipse Update Manager). This would be accomplished by adding a plugin dependency without v

design for transparent plugin downloading

2005-05-04 Thread Brett Porter
(first draft, after initial feedback I will turn it into a doc, likewise for the lifecycle). We have a feature in m2 that will take the prefix of a goal name eg "idea:idea" -> idea, and discover the plugin either locally or remotely and use it. Currently, it is hardcoded to org.apache.maven.plugin