After porting to 1.4, neither of the above jars files should be a problem when I provide a precompiled jar-file on the xmlbs site. I am not sure where mmbase stand now on the 1.4 issue, can anybody enlighten me?
For MMBase 1.7 you already need JDK 1.4, IIRC. So that would not be a problem.
I don't like to add mmbase centric code to this codebase since it will add undesired build dependencies. A precompiled jar-file should be easy to work with from an mmbase point of view and the wordhtmlfilter should probably be moved from the speeltuin to the modules or util or whatever package.
Well, it's trying to find what package to drop it into that may be a bit of a search. We are talking one class, a bit overkill for a full application tree perhaps, but not suitabel fro a generic 'tools' package as it depends on an external lib.
The suggestion was not so much to make it part of the code base, but make it a separate class/jar that you could, for instance, download from the xmlbs site, as an extension.
Maybe someone else has a better idea, or people find the idea of a separate application now so bad?
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
