> > The main disadvantage is I suppose that it doesn't 'feel right' to check > > external products in CVS. and that all kind of stuff should also be > > checked in because they must be distributed together or something like > > that. > > A big -1 for this.....(large) binary files do not belong in cvs, because > cvs isn't good at handling these files.
Are you talking form experiance? I have been doing that for ages.. (just co speeltuin/keesj) or wiab where mmbase is "just an other" .jar we need for site created a long time ago like worldpressphoto the hole site + "mmbase application 1.0" + orion + mmbase sources are in CVS (that's the only way to be able to maintain the old stuff) as long as you add the binaries as binaries "-kb" the "problem" doesn't exist IMHO > > Another idea good be to put these jars somewhere on mmbase.org, but this > could give some licensing problems, because iirc the idea was to start > using the j2ee package for developing, this may not be redistributed. I said I would look into that or have you already? I haven't followed the java 1.3 1.4 diffs but in 1.4 pooling datasources is standard for 1.2 you can download the jdbc-std-ext and there are "open-source" pooling datasources What can be in cvs or on the mmbase web-site? > > Gerard
