Ernst Bunders <[EMAIL PROTECTED]> wrote: > We must guard against creating 261 or so installable modules that together > will form mmbase. One of the issues that should concern us is that mmbase is > not a very clear product. three types of utility classes is not going to > make us score points in this direction
That was actually more or less my point. I wanted to say that _if_ were are going to spit of utilities, where will it stop then? And _if_ we 're going to do it, we should to it rightly, and in a logical and useful way isn't it? Splitting of one 'utils' jar, for both reasons (either you need the util but not mmbase, or you need mmbase but not the util), is possible, but I wonder what the point might be, because in both cases you can simply put the monolithic mmbase.jar too. The other reason might be that you might fancy seperate versioning, which seems to me a bit silly because the 'util' package will be very diverse, and contain a lot of independent things. Michiel -- Michiel Meeuwissen Mediacentrum 140 H'sum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
