8. November, 2011
If you’re with a big company and want to do it “right”, chances are that you’re only allowed to deploy during the night, on weekends and never, never, never in December (or any other date were mission critical systems must not fail).
Looking for some reasons why this is wrong? Go here: Why are you still deploying overnight?
In a nutshell: You’re deploying overnight because your processes are brittle, the product is riddled with bugs and you have no fall-back strategy.
Overnight deployment is nothing but a red flag saying that you’re not doing it “right”.
16. March, 2010
If you’re like me and use Tomcat and you want to bring down the size of your WAR, you’re faced with one issue: All your applications need to use the same libraries (since there is only a single common/lib for everyone). So you’re either stuck with an old version or you need to upgrade all your apps at the same time. I just can see the budget guys shake their heads.
The solution is a list of directories in your context.xml which contain specific versions of the libraries you need. This way, you can install all the versions you need and each app can pick and choose.
For the complete solution, see the original article: Extending Tomcat WebappLoader to Share Library jars
OSS for teh win! :-)
8. March, 2010
Here is a nice post by Julian Simpson about how to manage your runtime dependencies (i.e. programs and libraries which your code expects and which you can’t handle with, say, Maven): A way to cool dependency Hell?