zoran wrote: > specific: what should be core/base and what should be external.
Well, e.g. to start with I'd say that all classes in org.mmbase.util which are not used by mmbase core itself, can be moved to a seperate app. But I would be reluctant to do so, because for the moment it will only create problems, and doesn't solve a thing. E.g. the taglib app. will then depend also on then util-package. We'll have to fix that then too. We will encounter problems, which I am not wanting to solve, especially not while the 'maven' decision is pending, and am not willing to invest in the current mechanisms on that area. As a example I think this is bit similar to the introduction of the 'contribution' CVS module. Although that decision may have been principally correct, in practice it only makes my life harder, because I don't have one target to create every jar now, and the number of times on which I forgot to upload mmbase-aselect to the server is countless. Just because it does not automaticly appear between the other jars any more after a full build. What I'm saying is, why are we insisting on making life more difficult, especially when there is _no_ practical gain. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
