For a few days now, I’ve been having issues validating the “Server Home” path within VS Code - Adobe Coldfusion Builder Extension when the path is using a Commandbox server. Here is the full path I’m using on my end:
c:\Users\aze\.CommandBox\server\8AF581728159D384F5AFF6B89868A772-API-Projects\adobe-2018.0.13.329786\WEB-INF\cfusion
Is there anyone else running into a similar problem with the newly deployed VS Code Adobe Coldfusion extension? Has anyone found a solution to this issue?
Can you try pointing to just the WEB-INF? Perhaps Adobe wants you to point to the folder containing cfusion
same error. I was able to test with an Adobe Coldfusion installation and it does work fine and defaults to the “/cfusion” folder. Could it be the “.” in the “.CommandBox” path?
Hard to say, I’d reach out to Adobe and see if they can confirm the correct path or provide additional information as to why its not working. I know other people have gotten this working.
I realize this is old, but people may find it searching for the solution. It’s that CFBuilder’s check of that server home folder looks for it to include a jvm.config file in the bin folder under that server home…which commandbox does not have.
If you just create an empty jvm.config in that WEB-INF\cfusion folder (see the original post here), that will allow CFB to let you get past that screen. (Commandbox won’t be bothered by it, and since folks would rarely look into that folder it shouldn’t confuse too many humans. 
)
If Brad or anyone might offer a point of contention on that, do let us know.
Excellent information, Charlie! I don’t understand why Adobe would have forgotten about J2E installations of ColdFusion, but creating that file would not cause any issues for CommandBox-- and of course, the file would not be used for anything.
