Just to chime in, I think I have seem build scripts that always ran the om task as part of a larger build. Maybe not the right way to do it, but seems to make things more idiot proof. The only handicap was that it made the build longer, so this would help speed up the build.
I believe build scarab is like that. Eric -----Original Message----- From: Kurt Schrader [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 1:46 PM To: Turbine Torque Developers List Cc: [EMAIL PROTECTED] Subject: Re: cvs commit: jakarta-turbine-torque/src/conf default.properties build-torque.xml What good does this do us? All that is going to happen is that people are going to run the "om" task and not have anything happen and then not know what's going on. Presumably you only want to run the "om" task if the schema has changed anyway. What is your use case for this? -Kurt On 21 Aug 2002 [EMAIL PROTECTED] wrote: > stephenh 2002/08/21 10:33:14 > > Modified: src/conf default.properties build-torque.xml > Log: > Added a torque.runOnlyOnSchemaChange property, defaulted to false, that when true will only run the om and sql targets if the schema has changed since their last generation. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
