Hi, I just got done using Torque for the first time on a project and am really looking forward to using Torque on another one I'm starting.
However, as I'm setting up the project directory structure, I'd rather not include the entire Torque directory structure in the application. I'd much prefer a drop-in approach, perhaps something Maven-like that delegates out to a central torque.home directory. I've looked at Scarab and I like it's approach of keeping the zip file in the lib dir and then unzipping it when needed. The build file for Scarab is very impressive and I like everything it accomplishes. However, I'd rather not include all of the complex functionality in each individual project's build file. In general, would it be possibe to move Scarab's build functionality into Torque itself? My current thinking is that there would be just one Torque jar file that besides the Java classes, includes the templates and other misc. files, much like the Torque zip file in Scarab's lib directory. Then when generating the om classes, instead of unzipping all of them to the hard drive like Scarab does, the templates and what not could be pulled directly from the jar file (probably with the InputStream mechanism in the java.lang.Class class that loads files from the classpath?). This would keep the user's project directories clean in that they would only have their project-specific files (e.g. Torque.properties and schema files) which the paths for are passed to Torque via properties. In addition to keeping all of the files in the jar file, all of the cool uptodate tasks could be merged into the default Torque build file instead of layered on top of it like it is in Scarab. And ideally it'd be configurable through properties (e.g. torque.keepuptodate = true/false). This email is getting longer than I'd like, but there are three basic ideas I'm looking for comments on: - Having a central torque.home location like Maven - Having a single Torque.jar that loads the templates from within itself (ideally without first extracting them to a temp dir) - Including the uptodate functionality of Scarab in the basic Torque install If these options are viable, I'd be willing to volunteer to trying to make them work. Or if someone already familiar with Torque would like to take over, that's fine, too. I just wanted to propose the ideas to the list and see if they're viable and that I'm not missing any obvious faults that would make the solutions unworkable. Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
