I am attempting to create a new project in ColdFusion Builder 2018. It is giving me the error, “Invalid project description.”
I have done the following steps:
(1) Choose /File | New | ColdFusion Project
(2) Chose BLANK under System Templates
(3) Set Type to NONE
(4) Clicked Next
(5) Set Project Name: Learn_CF_In_a_week
(6) Unchecked Use Default Location
(7) Set Project Location to C:ColdFusionBuilder2018ColdFusioncfusionwwwrootlearncfinaweekwww
(8) Set CFML Dictionary Version to ColdFusion 2018
(9) Clicked Next
(10) Set Servers to defaultLocal
(11) Clicked Next
(12) Left the Addional Source blank
(13) Clicked Next
What am I doing wrong? Where would I enter this ‘project description’?
Thank you in advance,
Mark
There seems nothing wrong with any of the steps you list. Instead, it seems to be related to one you do not: the “workspace” you identified for cfbuilder, and/or the existence already of a project where you are trying to create it.
A bigger point to help you and readers find such problems and more detail on solutions is to note that cfbulder is really Eclipse under the covers. As such, if you search for that error (without mentioning cf builder), you readily find discussions.
And the first (at stackoverflow) offers info on this idea of changing workspaces, or importing any existing project:
In particular, see the simple steps to either change the workspace or import an existing project at this particular answer there :
https://stackoverflow.com/a/41086232/90802
If your use of CFB is new, there would be no negative to creating a new workspace. (And for other readers, you could easily switch back to the old workspace if you take note of its path.)
Finally, one may say “why doesn’t someone just fix the problem”, or at least the error message to be more helpful. Again, though, this is not an Adobe or CFB problem, but an Eclipse one. Being an open source tool with millions of users, it’s indeed curious that a problem like this–or at lease the spartan error–could linger for so many years.
Let us know if that solves it for you, Mark.
You must be logged in to post a comment.