There are special ant tasks for deployment and undeployment. I guess you should use those and not just put stuff where tomcat should pick them up for you.
On Thu, 16 Dec 2004 10:56:22 -0600, Durham David R Jr Contr 805 CSPTS/SCE <[EMAIL PROTECTED]> wrote: > > I am not really an expert but I think it is beter if you modify > > your application at another location and then redeploy it on > > the server. > > > Heh, I think I know what you're saying. Yes, I modify the application > at a different location than deployment. Just for example, code that > I'm working on might go here: > > E:\projects\application\src > > Then an Ant build script would put the compiled/configured stuff here: > > E:\projects\application\latest-build > > Tomcat, for development purposes would be configured to look at code in > the "latest-build" directory. However, if: > > antiResourceLocking="true" > > in the Context (I made an error in my previous message and had this set > to "false"), then changes that are deployed to "latest-build" are not > picked up by Tomcat. Considering that antiResourceLocking, to me, is a > developmental feature (as opposed to production), then changes should be > picked up. Perhaps I should post a feature request? I'm really only > posting here to make sure that I'm not doing something wrong, before > something is sent to dev. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
