Re: creating a script module / libs in CVS

[Gerard van Enk]

Michiel Meeuwissen wrote:

<zapped>

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')

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.

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.

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.

Gerard