Michiel Meeuwissen wrote: > Another option would be to simply put only 'build.xml' in the root, because > that is the most interesting script anyway.
+1 > Yesterday on IRC also the idea of putting the stuff in CVS which is now > auto-downloaded in the build.xml came up (again) (say a module 'lib') Maybe call it 'ext' (external products/packages/resources) if we want to put the tar.gz and zip packages in cvs which we expand using the build.xml. Or do you only want to put the jar's (extracted manually from external packages) in cvs? > This has some obvious advantages: > > 1. The build.xml can be considerably simplified > 2. It is garanteed that every version of MMBase can be recompiled easily, > because there is no chance that the external resources get disfunctional. I would be +1 to put external stuff in cvs or on www.mmbase.org so we can have those two advantages. Maybe advantage 2 can be better achiefed by putting them in cvs. This way we also aren't dependent on two things to work (cvs and http). And all commitors can put things in cvs, but not all commitors can put things on www.mmbase.org. Putting things on www.mmbase.org doesn't simplify the build.xml either. I'll go for putting things in cvs. Jaco
