This is not a topic that I address in the book, but I'll give you my thoughts.
My goal with any release process is to minimize the pain involved. Painful releases just discourage people from doing them, which in turn makes the release more painful.
So, which is more painful, war files or a directory full of loose files. To my mind, the loose files are far more painful. Old files can be left around. I might run into permission or case problems on a Unix server. To avoid these, I would want to move the old directory out of the way first, which definitely requires a cleanup process after the release is done.
War files avoid several of these problems, so present less pain. I'd therefore advocate for war files.
Michael T. Nygard<br /><a href="http://www.michaelnygard.com/" target="_blank" rel="nofollow">http://www.michaelnygard.com/</a><br /> <br />Release It! Design and Deploy Production Ready Software<br /><a href="http://pragmaticprogrammer.com/titles/mnee/index.html" target="_blank" rel="nofollow">http://pragmaticprogrammer.com/titles/mnee/index.html</a>
Joined: Dec 16, 2003
I'd advocate for war files as well, but unfortunately, due to the working procedures of the client we are sending the sw to, this is not possible right now.
subject: Release It!: managing different deployment strategies