On Wed, Apr 21, 2004 at 12:44, Jaco de Groot wrote:
[...]
I completely missed this thread, so sorry for the late reply. I don't know if there's any news about this issue?
See reply at the bottom.
I would like xmlbs to become a MMBase project or part of MMBase and make Remco commitor. I got the impression that Remco was willing to do so, but maybe I'm wrong.
I do like to become a committer and I did offer the code for inclusion into the mmbase source tree. There's 3 ways of doing this:
- full inclusion; introducing an mmbase package like org.mmbase.util.xmlbs, importing all xmlbs source and replacing the xmlbs site by a notice saying it moved into mmbase. - mirroring; same as above but I'll keep working on xmlbs in my private cvs and backport every bugfix and major change back to the mmbase pacakge. - handling it as an external library and change the license if necessary. I'll make sure the jar-file stays accessible and will keep the mmbase build process and wordfilter uptodate.
Currently I prefer the last option because it ensures xmlbs stays usable and accessible outside mmbase and it's the least amount of work for me but if somebody has compelling reasons to go for one of the other two options that's fine too.
I'd also prefer this option. If you're willing to change the license that would be nice (dual or triple license you were talking about iirc), because we could add this to the default build process without any license problems.
Gerard
