-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
folders on the C root directory return an exception #7152
Comments
consider escaping the command line argument - like one would need to do for anything containing spaces. Also, using forward slashes helps. Hopefully I get this right; I'm not often on a windows box:
|
Can confirm similar error when scanning files that install off the root of C: on Windows. Using quotes or escape characters still gives the same error with basedir does not exist. |
```
dir c:\test
```
Shows what?
…On Sat, Jan 11, 2025, 11:42 AM cbgabriel ***@***.***> wrote:
@cbgabriel <https://github.com/cbgabriel> see #7152 (comment)
<#7152 (comment)>
image.png (view on web)
<https://github.com/user-attachments/assets/ffc43dcb-35de-4b62-81cc-2f1f0fdb5f22>
—
Reply to this email directly, view it on GitHub
<#7152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGSVQRP3SJFIXJNTTXG32L2KFCV7AVCNFSM6AAAAABRUM6EL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVGMZDSMRXGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Directory exists and contains application files. Using quotes or escape characters scans folders in locations within "Program Files\test", "Program Files (x86)\test", etc. works fine but trying to scan anything directly off the root of the C:\ even if the folder path does not have a space gives the basedir error. |
Can you run ODC again but add the
|
|
Describe the bug
I attempted to run dependency-check on a folder that installs in C:. I reconfirmed this by trying to also scan Program Files with the same exception being thrown. I am unable to generate a log file, I received the same error.
Version of dependency-check used
The problem occurs using version 11.1.0 of the cli (cli, gradle plugin, maven plugin, etc.)
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.
To Reproduce
Steps to reproduce the behavior:
Run dependency-check on a folder in the root C:\ directory
Expected behavior
Previous version of dependency-check did not throw an exception when scanning a root directory folder.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: