You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the issues list for existing open or closed reports of the same problem.
Describe the bug
When attempting to scan a folder with a space in the name, or output to any folder, errors arise:
Invalid 'scan' argument: 'C:\Program Files\Adobe" -o C:\Users\kent.viscount\Documents\Testing_Tools' - path does not exist
I have tried Powershell, Command Prompt, escaping the spaces with a , /, and ^. I have surrounded the paths in single and double quotes.
This did not start for me until today.
here are the commands I have used:
.\dependency-check.bat -l debug.log -project Adobe -f CSV -f HTML -s 'C:\Program Files\Adobe' -o C:\Users\kent.viscount\Documents\Testing_Tools
@jeremylong the forward slashes in the scan path worked. If there isn't a plan to fix this in the near term, can instructions be added for Windows users
Precondition
Describe the bug
When attempting to scan a folder with a space in the name, or output to any folder, errors arise:
Invalid 'scan' argument: 'C:\Program Files\Adobe" -o C:\Users\kent.viscount\Documents\Testing_Tools' - path does not exist
I have tried Powershell, Command Prompt, escaping the spaces with a , /, and ^. I have surrounded the paths in single and double quotes.
This did not start for me until today.
here are the commands I have used:
.\dependency-check.bat -l debug.log -project Adobe -f CSV -f HTML -s 'C:\Program Files\Adobe' -o C:\Users\kent.viscount\Documents\Testing_Tools
.\dependency-check.bat -l debug.log -project Adobe -f CSV -f HTML -s C:\Program^ Files\Adobe\
.\dependency-check.bat -l debug.log -project Adobe -f CSV -f HTML -s "C:\Program Files\Adobe"
Version of dependency-check used
The problem occurs using version 12.1.0 of the cli
Log file
When reporting errors, 99% of the time log file output is required. Please post the log file as a gist and provide a link in the new issue.
Log file will not generate with -l/--log options selected
To Reproduce
Steps to reproduce the behavior:
Expected behavior
dependency-check should be able to read the folder paths and complete
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: