Purpose of running Torque from a jarThe standard practice for using Torque has been to download the jar, unjar it to get the directory structure given in the user guide , and somehow either integrate your source tree and Torque's un-jared directory structure. While doable, this was less than desirable, especially when working with prespecified directory structures, such as that used by Maven. Complex build scripts, such as Scarab's , which dynamically unjar Torque during the build process and copy over all the correct files, can get around this, but having to re-develop or even copy such capabilities on a project-by-project basis is undesirable do to the relative complexity.
Instead, it is possible to run Torque without un-jaring it. All that is needed
is the venerable
Requirements
Along with the
Along with the classpath, you must edit the
Note , if you set only the above properties, Torque will default to using the old directory structure to read and output files from. This maintains backwards compatibility, but is not always what is wanted. The next section addresses telling Torque where to read and output files. Configuring DirectoriesThe following directory properties allow you to control with a good deal of granularity where Torque will read and output files. The table contains each of the properties, along with it's default value and description.
Invoking Torque
Once the build properties have been set, you can invoke torque via the
Also, a few of the Torque targets, currently om and sql, are smart enough
to not run unless the schema has changed. This would allow you to automatically
call
Example using Jar'd Torque and MavenFor an example of how to integrate Torque within the build process, see the Maven Howto . |