At least I cannot think of even one actual concrete problem with that.
Perhaps the only one is that it would slighty increase the size of
mmbase.jar with a few bytes, but come on, really, we can't seriously call
_that_ an important issue.
That is not what is see as the issue.
My issue is that, by including all kinds of non-core implementations,
you do not actually create a 'Core' MMBase, but a 'Junk' MMBase.
You cannot draw a line if you include these 'example' classes.
It's a matter of design choice, and I think that it is worth discussing.
If people think design and architrectural choices are not worth
discussing, then I wonder why we have this list at all?
We can decide to move such classes (but then _all_ such classes) to a
seperate app. Though I dont' really see the point even then, I don't
disagree.
So we're at the point of defining what 'such classes' means. Or more
specific: what should be core/base and what should be external.
You can't critize Andre on that though, he just follows current practice.
I agree: consistency over correctness! Lets define correctness :)
Regards, Zoran
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
