wood burning stoves 2.0*
The moose likes Agile and Other Processes and the fly likes Release It!: managing different deployment strategies Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Release It!: managing different deployment strategies" Watch "Release It!: managing different deployment strategies" New topic

Release It!: managing different deployment strategies

Gian Franco
Ranch Hand

Joined: Dec 16, 2003
Posts: 977

How would you suggest to manage different deployment
strategies for different customers?

E.g. some clients would like their apps deployed as
a war, others prefer loose files (!), some apps are
hosted in-house and others at the clients site.

Is this manageable with the DRY principle applied
along the line in some way?

Kind regards,


"Eppur si muove!"
Michael Nygard
Ranch Hand

Joined: Jan 03, 2007
Posts: 40

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>
Gian Franco
Ranch Hand

Joined: Dec 16, 2003
Posts: 977
Thanks Mike,

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.

Kind regards,

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
subject: Release It!: managing different deployment strategies
Similar Threads
Two JVMs under one Tomcat
Why so much emphasis on Business Delegate or Intercepting Filter
Is Eclipse really this hard? And how did it get so popular?
is it possible to distribute a servlet based application?
best practices in moving webservice or other apps across environments