Nevermind. It bugged me all morning trying to remember why someone had raised a licensing issue, and I finally recalled the actual issue, which has nothing to do with James. The Thomas Mueller advertising clause prevents HSQLDB from being proposed for Incubation as an ASF project. It has no effect on our being able to bundle hsqldb, since that is addressable in the NOTICE file, and it would not be a hard dependency.
The irony of this whole discussion is that I brought up the idea of incorporating HypersonicSQL/hsqldb two years ago, so that we could depend upon the presence of a SQL database: > Honestly, I'd love to can file system user repositories in favor of > at least using HyperSonicSQL bundled with James, but there does not > appear to be any consensus to do that. ref: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] .org&msgNo=4123 > I'm hoping that in James v3 we will include hsqldb, so that we can > always assume the presence of a database ref: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] .org&msgId=647741 > > Having a JDBC database as a known part of the environment is > > getting better and better. > Heh, sure. Ok maybe we do this at least for configuration stuff. I know > embeding hypersonic (?) is something you'd like to see. ref: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] .org&msgId=591339 We already have HypersonicSQL support in sqlResources.xml. The current version of the HypersonicSQL block for Phoenix appears to be http://cvs.sourceforge.net/viewcvs.py/hsqldb/hsql-component/. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
