On Wed, Mar 4, 2009 at 13:09, Nico Klasens <[email protected]> wrote: > Hello Michiel, > > I have been playing around for some hours the last weeks with my preferred > maven2 build structure. I commited the head to a subversion and started > moving the files in the way I wanted it. See > http://nico.klasens.net/svn/trunk/mmbase/. > > Big advatnages. Simple poms which use the provided mojo's instead of our > own. Any level of rhe build can trigger a multimodule build. > I creatwd two mojo's. 1 for the INDEX files (copy of yours) and 2 an > RemoteGenerator for the rmmci build. > A lot is also usable in the current structure, but I would prefer somthing > like mine.
I think your proposal is preferable above what is now in CVS. Though on one hand I find some merit in our current, less complicated directory structure (src, blocks, template, config, vs. src/main/java, src/main/webapp, src/main/config), on the other hand this default maven directory structure is used more universally so probably more readily understandable. That using that structure also simplifies the pom's and largely obsoletes the Mojo I deviced is an argument too, though I must say that I found the amount of code to arrange everything quite modest. The big disadvantages of changing the directory structure is that you can't simply move things in CVS, so it would be best to migrate to svn first, and that it would be silly to try to keep the existing build scripts working, so I'd propose to simply drop those. These are hardly technical probems though. greetings, Michiel -- mihxil' http://meeuw.org nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
