. When come to deployment, what are some tips for version control
>>> Version control should not be very difficult as fortunately most components have the version number as part of the jar file name. Also older versions of a component can be easily downloaded from the Jakarta site.
I agree with having jar files under version control, however it is a pain when jar files have different names. e.g. when having the a version number attached to the jar.
1. if you dont have a version number then you can have it under real version control and check in a new version, promote or label it and all dependencies are fine. Downside to this approach is that you cannot see which version of the jar you are using. e.g. log4j_28.jar or log4j_27.jar since both files will be renamed/checked in and promoted as log4j.jar.
2. If you are using a version number in the jar file, be aware that you have to check in a new file, label or promote it, then make sure you do not label or promote the old one and make sure the dependencies in your projects are still ok e.g. in meta-inf directory files.
so yes you need to have the files in version control, but there are several ways to do it, all with downsides to them.