- Newest
- Most votes
- Most comments
The error message "Cannot find build artifact for the project" typically indicates that the security scanning tool is unable to locate the necessary files or artifacts for analysis. Here are a few suggestions to help resolve this issue: Verify the artifact path: Double-check that you have specified the correct path to the build artifacts, specifically the .class files. Ensure that the path is accurate and points to the correct location. Check the project structure: In a large enterprise project with multiple levels, it's important to ensure that the project structure is correctly configured. Verify that the build artifacts are generated in the expected location and that the scanning tool is looking in the right place. Build the project: If you haven't already, try building the Java project before running the security scan. Building the project will generate the necessary build artifacts, such as the .class files, which can then be scanned by the tool.
Relevant content
- asked a year ago
- asked 7 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago
I appreciate you answered. You've listed almost everything I've tried so far I tried all possible ways to specify the path to .war and .class files. I guess that is some kind of bug because some time I received another error "File extension xml is not supported for CodeWhisperer" although previously it threw "Cannot find build artifact for the project". It works perfect for the projects with modern tech stacks. But for old enterprise projects it needs more parameters for scanning folders.