I see. I don't know much about eclipse legal process, but XML:DB license should be compatible with EPL. Is it possible to check if xmldb libraries are going to be a problem?
It probably won't be too much of a trouble to remove dependencies on xmldb from xindice.core, but it also means that Xindice building process (and possibly code) has to change to separate server and client parts completely. The idea itself is not bad and can make it to official release some day, but customizing the code can make upgrading to the next version more difficult. Anyway, if I am not mistaken, xindice.core only uses two classes from xmldb: XMLDBException and ErrorCodes. The same two classes are used in xindice.server which is necessary for XML-RPC. There are also general-purpose packages, but they should not depend on xmldb... Also, XUpdate functionality (xindice.core.xupdate) depends on xmldb-update library so you won't be able to use that at all. I think that's it. Regards, Natalia On Fri, Oct 24, 2008 at 10:03 AM, <[EMAIL PROTECTED]> wrote: > Hi, thanks for your answer. > > The background of my question is that we think about using xindice in the > eclipse open source project SMILA. > The state of xmldb is not quite clear to me. As far as I know there exists no > release, yet. This may cause problems in eclipse legal process. > We have no special need for api 1), so if 2) and 3) could be made available > without the need for xmldb that would be a feasible solution for us. > > Would cleanup of org.apache.xindice.core.* be enough for this use case ? > > Bye, > Daniel >
