Re: release policy add on proposal: avoid dependencies on older maven releases

[Brett Porter <br...@apache.org>]

Irrelevant for m2 - nothing will depend on the maven core (but things like wagon
etc might have various versions floating around). Improvements to let
dependencies specify version ranges will help (so rc2+ would use rc3 if it were
already there).

As far as Maven 1.x goes, I'll hack the offending plugins to use the executing
version of maven instead.

- Brett

Quoting Jerome Lacoste <je...@coffeebreaks.org>:

> Make it sure that each milestone make it so that plugins reference the
> same milestone core. At least for the ones distributed with maven.
> 
> That would allow things like rc3 downloading rc2.
> That would improve consistency, and avoid having questions in the user
> list.
> 
> Otherwise where is the limit?
> 
> Do we want to distribute maven 1.1 with one plugin depending on rc2, one
> on rc3, one on 1.0 one on 1.0.1 one on 1.1rc1.
> 
> It is perhaps too much to ask?
> 
> J
> 

Re: release policy add on proposal: avoid dependencies on older maven releases

[Michal Maczka <mm...@interia.pl>]

On Thu, 2004-06-10 at 03:29, Brett Porter wrote:
> Irrelevant for m2 - nothing will depend on the maven core (but things like wagon
> etc might have various versions floating around). Improvements to let
> dependencies specify version ranges will help (so rc2+ would use rc3 if it were
> already there).
> 
> As far as Maven 1.x goes, I'll hack the offending plugins to use the executing
> version of maven instead.

And that is the right thing. Dependency on executing version of maven
should be presumed. It's not that easy as it seems to implement this.

Anything else  will be an attempt to fix the consequence not the cause.

Michal