Hello,
I've modified the build.properties and build-torque.xml so that Torque
can sit in another directory specified by torque.home in the user's
build.properties file and then a project's build.xml file delegates it's
Torque target out to the ${torque.home}/build-torque.xml.
Most of the ideas are from the Maven project; I think having a separate
Torque directory that's installed like an application on the system
instead of dropped into each project's source tree is more organized and
easier to maintain.
After browsing the Scarab build file, I also implemented it's uptodate
idea into the build-torque.xml file so that it will regenerate the OM
and SQL files only when the schema changes.
Though it's not related to the main refactoring of moving Torque into
it's own directory, within my own project, I also used some of Maven's
callbacks to integrate Torque within the Maven build process. In a
Maven-enabled project, just running "ant" will automatically check that
the schema is uptodate before compiling (the check is actually done in
the build-torque.xml as it's not Maven-specific).
Is there any interest in the modifications I've made? If so, should I
send the files as attachments or cut and paste the contents into an
email?
I'm certainly open to criticisms, both constructive and otherwise, to
the changes I've implemented. I'd really like to see this integrated
into Torque, but I know I've probably missed some things and got too
ambitious in my property renaming effort.
Let me know what I need to do next. Or if there's no interest, that's
fine, too...I think it's a great idea, but I'm a little biased.
Thanks,
Stephen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
