I think we are trying to avoid too much discussion of m2 beyond the developer base to avoid any misconceptions until it has solidified in the form of a first public alpha release, however I realise this would be a big issue for some users of maven.
Basically, the following will apply: - a branch of Maven 1.x will be supported for a reasonable period of time. This isn't currently defined, and will largely depend on the demand from the user base and availability of developers. This is no different to any other piece of software. - You can always continue using the release you have if it works for you and you really want to. We're not going to rm -rf www.ibiblio.org/maven without warning :) - upgrading to m2 should be much easier because a lot of stuff that currently needs to be coded into maven.xml may well disappear as the requirements have learned a lot of lessons from m1 use cases. Hope this helps, Brett > -----Original Message----- > From: Jerome Lacoste [mailto:[EMAIL PROTECTED] > Sent: Monday, 17 May 2004 1:45 PM > To: Maven Developers List > Subject: RE: cvs commit: > maven-components/maven-core/src/test/java/org/apache/maven/lif > ecycle/phase GoalDecorationPhaseTest.java > > > On Thu, 2004-05-13 at 08:16, Jason van Zyl wrote: > > On Thu, 2004-05-13 at 05:22, Heritier Arnaud wrote: > > > Why must we replace Jelly ?? > > > > > > Isn't it better to correct/enhance it ???? > > > > The short answer is no, it's not. It's not being maintained by its > > creator and someone would have to burn it to the ground and > rebuild it > > to make it decent. > > what will be the impact in terms of compatibility? Will that > requires many changes to the files in order to port them to m2? > > Jerome > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
