I agree with Vincent. A lot of big business have moved to Maven. As long as M2 is not as advanced (and eventually more advanced, of course) as M1, there is a strong need to continue to fix and improve M1.
On 4/30/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > > -----Original Message----- > > From: Arik Kfir [mailto:[EMAIL PROTECTED] > > Sent: samedi 30 avril 2005 04:00 > > To: Maven Users List > > Subject: Re: Timeline for release 1.1 > > > > Just wondering, is there a point in getting a 1.1 out, with m2 coming in > > three-four months? > > > > I, for one, would prefer that efforts go into making m2 better, faster, > > leaner, meaner rather than into another m1 release, that probably won't > > live too much after m2 is released...and don't forget the cost > > maintaining one or two bug fix releases for 1.1 so... > > You're kidding of course? I'm totally -1 to your idea. M2 is already a > pain > in the neck for everyone already using Maven that it is a duty for Maven > to > support as much as possible its existing users that it has attracted for > the > past 3 years. > > Also I think you don't imagine the effort there is for m2 to come even > close > to m1 in term of plugins. It's not only a question of number of plugins > but > also a question of the features and details each plugin has. > > Arik, you ay not realize but Maven is not a small and unknown open source > project and it is being used in lots of major businesses. Migrating a m1 > build to a m2 build is something that is far from being automated and it > will not happen before several years in lots of places. You want to keep > supporting these people and fix m1 bugs, etc. > > Now all that said, you're already right (unfortunately): most maven core > committers have already switched to m2 and are not helping much on m1. I > bless Brett for doing so. He's doing a lot of good to Maven as a whole by > continuing to support m1. Gladly we also have some m1 users that are m1 > plugin committers and that are continuing to improve/fix the existing > plugins. > > Personally I would like to see as much refactorings as possible to bring > m1 > as close as possible to m2 to make it an easier migration in the future. > This is what Brett has started by bringing the Model and Wagon to m1. > > I would like to see m1 plugins being refactored into plugins that can work > both in m1 and m2 (I think that ought to be possible in several cases but > we > would probably need to develop a small m1 adapter layer). Alternatively m2 > plugins could be made to work in m1 by adding this adapter layer. I'm > still > unsure whether this is possible but I've started experimenting with it. > > All that said, I'm also very excited to use m2. I have started to migrate > my > existing open source projects to m1 and I can do that because these > projects > are business-bound. I've also seen some limitations that currently exist > in > m2 and that will hopefully be fixed soon. > > Thanks > -Vincent, answering for all existing business users of m1 ;-) > > > > > > > Brett Porter wrote: > > > > >There are no plans at the moment. Since it is incorporating many of > > >the components from Maven 2 while remaining backwards compatible, the > > >current effort is going into Maven2. > > > > > >- Brett > > > > > >On 4/29/05, Gisbert Amm <[EMAIL PROTECTED]> wrote: > > > > > > > > >>Hi Maveners, > > >> > > >>can you already say when release 1.1 will be ready? > > >> > > >>Regards, > > >>Gisbert > > >> > > >>--------------------------------------------------------------------- > > >>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] > >
