OK, so... i'll give that a shot once I reformat it to the Maven code style!
On Thu, Jul 17, 2008 at 3:04 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > You would attach it to a jira at the mojo.codehaus.org project and then > try to get some mojo committer to pick it up. > > -----Original Message----- > From: Stephen Connolly [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 17, 2008 10:02 AM > To: Maven Developers List > Subject: Re: How do I go about contributing a plugin to mojo? > > Anyway, my question is how do I go about contributing this? > > On Thu, Jul 17, 2008 at 3:01 PM, Stephen Connolly > <[EMAIL PROTECTED]> wrote: >> one use case for this is when you have a suite of components and you >> want to force _all_ of them to the same version. >> >> Perhaps you have several suites of components and you want to force >> all the components in each suite to the same versions across the >> suite. >> >> On Thu, Jul 17, 2008 at 2:56 PM, Stephen Connolly >> <[EMAIL PROTECTED]> wrote: >>> And then when you want to roll a release? >>> >>> Anyway, if that was the case why is it that most of the maven plugins >>> themselves use this pattern? >>> >>> e.g. <version>${maven.version}</version> >>> >>> Also you may want to force all one set of components to the same > suite >>> release... so blah-core may be only available at 1.3.5 while >>> blah-logging may be at 1.3.7 >>> >>> -Stephen >>> >>> On Thu, Jul 17, 2008 at 1:52 PM, Michael McCallum <[EMAIL PROTECTED]> > wrote: >>>> why not just specify the dependencies with version ranges, if you do > there is >>>> no need to rewrite anything it just works... >>>> >>>> On Fri, 18 Jul 2008 00:35:17 Stephen Connolly wrote: >>>>> >>>>> Oh... and if you want to prevent jumping too high in versions or > too >>>>> low, it supports adding a version specification to limit things. >>>>> >>>> >>>> >>>> >>>> -- >>>> Michael McCallum >>>> Enterprise Engineer >>>> mailto:[EMAIL PROTECTED] >>>> >>>> > --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
