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]
