It seems wrong to put it in the hsql block (because it's specific to the db samples). So I guess in the db block. That makes the hsql block build (presuming that's where the hsql script call goes) depend on the database block, which is fine as you point out.
Agreed - but I am really not in favor of the hsql script call. This call has to happen at runtime not build time :-/
> Am I right that "block"
dependencies are not dealt with yet, since we don't really have blocks but sub-builds called "blocks"?
AFAIK - yes
So I propose just to split the cocoodb.script into a standard sql and a hsqldb specific init script. Then let ant merge them and put them into WEB-INF/db whenever the database block is included.
I don't think it's too bad to have the database block copy that tiny sql file into WEB-INF/db even if no hsqldb is installed.
We can solve this later with the block dependencies...
We could link to a documentation page from the samples where we describe how to setup the database examples to work with other datebases. Then we don't have the hassle with the sql compatibility and the users should also be fine. -- Torsten
