ColdFusion Builder Extension Contamination
Posted under: 
ColdFusion Builder Beta users should be aware when using ColdFusion Builder Extensions, the extension files/folders are being installed in a ColdFusion server's web root that the user selects. This may contaminate your web root with files and folders not relevant to your application releases. It may not be a big deal for you (SVN users could ignore the folders/files) but I would suggest creating a seperate ColdFusion server instance to house Extensions. Any thoughts?
Well, I would doubt that you are going to host extensions on a production box. What I do is simply use my web root, my default web root. I've got N projects, each with their own web root, each set up with hosts like dev.foo.com, but then I keep my main web root (http://localhost) for pure testing. I just dump my extensions in there.
Hmmm interesting. So I wonder what happens if more than one person points to the same CF server to house the extensions on? We don't develop locally at my job; we all share the same dev servers.
@Ray - sounds like the same @ my work so it wouldn't be a problem. It comes down to your build process and development environment setup. Key is making sure the extension files don't accidentally get pushed from development to another environment (qa, production, stage, etc).
@Stille - I think, I maybe wrong, but each developer would have to import the extension after it is initially created on the development server.