On 11/8/05, Patrick Branley <[EMAIL PROTECTED]> wrote: > 2. have source code set up with mapping as a variable that get replaced > dynamically by a build script. > > cons: > extra time to write a build script to do this for every application > source code cannot live on a dev server and instantly be ready for > testing/development - you have to 'build' your code to run it. its no longer > as RAD as it used to be.
You only need to write the build script once and customize the properties in the file to suit that particular application's environment. Ant is a piece of cake to learn and ridiculously powerful. If you're using CFeclipse then the expensive "build" process you refer to involves clicking a single button once and waiting a few seconds - not too bad, really. :) If using build scripts will solve your problem then I highly recommend going that route. If you ever get into test-driven development (unit testing with CFCunit, CFunit, etc) then you can plug all those tests into your build script and prevent bad code from ever touching the server if it fails the unit tests. Ant is truly a beautiful thing. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
