Why doesn't CFEclipse let me work, how I did in HomeSite, CFStudio or Dreamweaver?
This question keeps coming up, Why doesn't CFEclipse do this, or that. I can't start to use CFEclipse full time till it allows me to do this or that.
Well, my answer to this is: How come there are already a great number of CF Developers using CFEclipse without a problem? The reason: they changed the way they developed to fit with CFEclipse.
Why did they do that?
Eclipse allows you to develop your applications from one IDE, everything under one roof. DB Support, CF Coding Support, HTML, Ajax and CSS Support why have 4/5 Applications open when you can have one.
The way they were developing was bad, The original development tools, and CF it self in the early days allowed us all to use Bad Practices and many CF Developers seem to have stuck to this.
What do I mean by Bad Practices
I've heard Developers say with pride that they edit code on Live servers, my normal response to that is, oh so your new to development? Then you hear “no, I'm a senior developer and I've been working with CF for over 4 years”. WTF!!!!!!!!!!!
OK I'm no angel, I've edited code on a live server, and I've stopped a whole site from functioning, but not for a while now people! I've seen the light, and so should you. If you think editing code on a live server is cutting-edge then sorry but it's time you left the Developer scene. OK I don't mean to be harsh but really it's not hard to change the way you develop and place some process in to your workflow, even if you are a Single Developer. At the end of the day, the time spent setting up at least two environments other then your live environment, and the time you spend deploying code to these environments, will far out way the time you spend fire fighting your live application, and give you more free time.
Trust me, I've been there and done it and now I feel a free man!
So what are these two environments?
That would be a local development environment, and an integration environment. These at the very least will help you identify faulty code, once you have moved code from local to integration you will find the files you forgot about and see the hard coded variables you've left in your code (Again a bad practice but as you do this you will stop it and learn).
Once you start the ball rolling, trust me you will want to move faster and faster, into using Unit Testing, SVN, Ant and Bug Tracking. Even if you are a single developer you never know when you will need to expand to another developer and another and another. So if you put the ground work in now, life will be easy.
Just remember CFEclipse is a great tool, yes it doesn't have all the features that HomeSite , CF Studio or Dreamweaver has but then CFEclipse has a few that they don't either like the Framework Explorer and great SVN Integration (OK More of an Eclipse thing then CFEclipse) I guess I will have to go over using CFEclipse in my Tutorials in Vision over the next few weeks to show why you should use it, why you should drop your old bad practices and come join the masses and find more time to yourself 
At the very least come to Scotch on the Rocks 2008 and learn from the best, and ask the questions that just haven't been answered that you feel embarrassed to ask on the open net.
Be the Best, Be at Scotch 
Definitely good points. I am a CFEclipse convert. It did take me some take to make the transition (mostly learning new keyboard shortcuts). Even so, I think Mark Kruger gives a good alternate viewpoint: http://www.coldfusionmuse.com/index.cfm/2008/1/18/Coldfusion.IDE.projects.vs.workorders