I talked to Preston offline and he explained all the different projects and its use. VXQuery-cli is has only one java class that has all the code that deals with command line interface, and the way path is set up can actually be seen in pom.xml. Maven resolves the all dependencies and redirects to target and so on. CLI calls everything in core. All the actual code for VXQuery and rewrite rules are written in classes in core. Server creates VX-Query server, data nodes and scripts to start the cluster. Benchmark has the weather benchmark and eventually support XMark Benchmark. XTest is the test suite, that is, has all the test cases for testing all XQuery specs and functions. ᐧ
On Sat, Feb 14, 2015 at 3:08 PM, Shivani Mall <[email protected]> wrote: > I just set up eclipse with the vxquery code. I am trying to understand the > packages and the folder structure and trace down the command line( > vxquery-cli/target/appassembler/bin/test.xq: for testing a file) in the > code base packages, but I could not find the right path. I also noticed > that there are dependent projects with same names: cli, core, server and > almost the same folder/ names of java files as inside the master vxquery > project. Is there a documentation that I can read to understand how in the > code does it find the right path and execute for a specific query? ( I am > sure I am misinterpreting things here.) > > Also, the java docs are helpful but what (project/package) will be a good > place to start to understand the code from the base level? > ᐧ >
