Skip to content
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

Scanner not picking the build.gradle file but scans the other jar files available in the repo #7274

Open
arunkumar-thangavel opened this issue Dec 26, 2024 · 1 comment
Labels

Comments

@arunkumar-thangavel
Copy link

We are using the home brew version of dependency-check and when we try to scan a repo using the below command, it picks jar files from sub folders but not grabbing the build.gradle file to scan the CVEs.

dependency-check -s “projectPath” --enableExperimental -f JSON -o MyRepo.dep-check.json -n

is it the expected behaviour or do we have to do additional configuration to make it pick the build.gradle file?

@jeremylong
Copy link
Owner

The CLI should not used to scan gradle projects. Use the gradle plugin instead. If you really must use the CLI, then you have to run something like a copy dependencies task. Either way, if you likely need to modify the build.gradle or use an init-script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants