Ralph, We have three environments: a development environment where we develop/test our sites and a test and production environment at our clients. Copying the files from develop environment to the test environment at our clients is being done by making update zipfiles which only include the changed scripts that we find by sorting all the scripts by date/time. And only the scripts in the development environment are being checked in a version control. Now I want the test and production environment to use caching ofcourse but not in the development environment.
Greetings, Gunter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ralph Einfeldt Sent: dinsdag 13 augustus 2002 14:27 To: Tomcat Users List Subject: AW: Turn off caching Sorry didn't think about that, because we don't run our sites directly from the workspace of our version management. We have jobs that copy the files from the workspace to the runtime environment so we can do what we want in the runtime environment without impacting our buildmanagement. Which of the two approaches do you use ? I would guess that the second one shouldn't mess up your version management. (At least everything under the work directory shouldn't be a part of your build) > -----Urspr�ngliche Nachricht----- > Von: Gunter D'Hondt [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 13. August 2002 13:53 > An: 'Tomcat Users List' > Betreff: RE: Turn off caching > > that works perfect but the problem is that I cannot use this > method when using a version manager tool becoz it would > always believe that all scripts are updated and we cannot see > which scripts are being changed. > > currently we are using your solution but I'm looking for a > better one... thnx anyway! > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
<<attachment: winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
