Mailing is something which you may want to do in a lot of applications, and the one interface with 2 implementations are hardly bloating mmbase.jar itself.
The point is: is sending email a core functionality of MMBase?
I think it is not, so I don't think it appropriate to have a mail implementation in the core. I prefer one email application.
If there is to be a core email functionality it should be something that is simple (just send an email using java mail) and works.
But I prefer to not have an implementation in the core myself.
E.g. I think a 'Tools' application may perhaps not even be worth the trouble
because you may end up needing it always, and only gain the hassle of
defining the dependency all over the place. I wouldn't mind if traditional
and widely used MMBase features like jumpers, posrel and mmevents simply
remain in 'mmbase core'.
Personally I would like to get rid of stuff like AnnotRel, XSLConvert, or RelativeTime. I have never used MMevent.
Jumpers can be useful. PosRel is often used. NodeComparator may eb sueful enough to kepe as an utility even though only the Community applications currently uses it.
If people don't like a tools app, we need tyo chosoe what to do with these remaining classes.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
