Status/Resolution/Reason: Closed/Withdrawn/UserError
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 08/01/2016
Components: CLI
Versions: 2016
Failure Type:
Found In Build/Fixed In Build: CF2016_Update1 /
Priority/Frequency: Major / All users will encounter
Locale/System: ALL / Win 64
Vote Count: 0
This is similar to 4126392, and I don't know how Adobe didn't notice and fix this when they fixed 4126392. Well other than being a bunch of jobsworths, I mean.
So after returning to CF after a hiatus, I needed reminding how the command line worked. So I typed:
cf.bat
And I was given these instructions:
Usage:
cfcli.bat <absolute or relative path of cfm> <positional arguments and/or named arguments, if any> -outputdir=<output directory> -logdir=<log directory>
Example1: cfcli.bat C:\Project\hello.cfm
Example2: cfcli.bat C:\Project\hello.cfm foo
Example3: cfcli.bat C:\Project\hello.cfm name=bar
Example4: cfcli.bat C:\Project\hello.cfm foo name=bar
Example5: cfcli.bat C:\Project\hello.cfm -outputdir=C:\Project\classes
Example6: cfcli.bat C:\Project\hello.cfm -logdir=C:\Project\logs
Example7: cfcli.bat C:\Project\hello.cfm -outputdir=C:\Project\classes -logdir=C:\Project\logs
Example8: cfcli.bat C:\Project\hello.cfm foo name=bar -outputdir=C:\Project\classes -logdir=C:\Project\logs
It's not cfcli.bat. It's cf.bat. There is no such thing as cfcli.bat.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 4177334
External Customer Info:
External Company:
External Customer Name: Adam Cameron
External Customer Email:
External Test Config: My Hardware and Environment details:Attachments:
Comments: