I think that if it's not broken, don't fix it. One (and probably the most important) feature of maven is to formalize the build process. But it seems to me mmbase has a formalaized process allready. If we want to put effort in it we could do that by documenting it's features so the formalization becomes obveous to all. Perhaps we could make testing more important (test fale, build fale). I think things like the website maven generates (and one of my favourites: instant eclipse project) is a nice to have, and no good reason to rework the build process. Maybe a merge between mmapps and mmbase cvs could be a good reason, but otherwise?????
Ernst > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Pierre van Rooden > Verzonden: dinsdag 24 mei 2005 9:54 > Aan: Discussion list for developers > Onderwerp: [Developers] Maven project? > > > So, after Nico's presentation at the dev meeting, what do > people think > of the use of Maven for MMBase? > > -- > Pierre van Rooden > Mediapark, C 107 tel. +31 (0)35 6772815 > "Anything worth doing is worth overdoing." > _______________________________________________ > Developers mailing list > [email protected] > http://lists.mmbase.org/mailman/listinfo/developers > _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
