On 4/2/07, Rick R wrote: > The tricky part is cases where applications share files .... for example, I > have an "include" directory at my web root which contains images, css files, > and a few cfm files that are used not only across various applications > within the main web site, but across multiple web sites as well through the > use of IIS virtual directories and coldfusion mappings.
SVN:externals is FREAKING AWESOME. Just what the doctor ordered for those trickier situations... check it out... As for repositories for each project, the only thing to keep in mind is that the JavaHL interface cannot commit across repositories. The SVNkit interface doesn't have that limitation. Not much of a limitation, boils down to committing changes for each project, vs. all projects at once. As always, the PITA of linking or sharing components is that you gotta really test everything that uses that component whenever you make a change to it. It's harder to stage roll-outs when code is shared, and mapped, etc. It's a good recurring thread, that one about "do all projects move along as you do, just the ones you're currently working on"... pluses and minuses either way... but a HUGE incentive for unit testing, etc., if you DO go the route of "we're all going!" or "if I'm going, I'm taking you all with me" type deals... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274378 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
