> It occurs to me that the “vm” module doesn’t depend on other calcite modules, > and vice vers
Suppose we add H2 database test DB. This database works of a file system, and the file name is given in the JBDC URL. If the "vm" project is checked out to some random location, it would be hard to make Calcite tests know the location of the database files. Well, a set of properties or environment variables can solve that, however it would stand in the way. We could add "/vm" folder to .gitignore and recommend checking out the VM project there, however it might play better as a git submodule. Vladimir
