J W wrote: > I am looking to have better version control at our company and am wonder how > YOU deal with this. What is your setup?
Local development against a local CF and local resources. Full working copy of a SVN repository. Code gets tagged in the repo and then a build server will use an Ant script to pull in drivers, externals and configuration files and generate several EAR files, both a compiled and a source version for each CF version supported. Source versions go to the test environment and when approved the compiled version goes to the staging environment where the customer will approve it for final deployment. I second the recommendation for SVN as a centralized versioning system but you shouldn't pay too much attention to all the people claiming it is hard to set up. It may be tedious when you do it for the first time, but not hard, you just have to follow the manual. And be warned about all the blogs and wiki's too: I'm sure their authors write them with the best intentions, but few of them add something that is not in the manual, most of them are outdated and none of them cover important issues such as the proper way to secure and backup your repository. And don't even think about using that one-click installer, version 1.2.3 is ancient and binary incompatible with the current versions. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get involved in the latest ColdFusion discussions, product development sharing, and articles on the Adobe Labs wiki. http://labs/adobe.com/wiki/index.php/ColdFusion_8 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:290438 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
