Allow analysis.json to be produced even when gradle/gradlew or mvn/mvnw fail to execute #93
Closed
Description
Is your feature request related to a problem? Please describe
Currently, some issues that happen during the copy of libraries phase happen, it stops the code analyzer from generating an analysis.json file. For instance, gradle or maven is not installed or no gradlew or mvnw in the project, but I imagine that other issues with gradle/maven can stop code analyzer execution too.
Describe the solution you'd like
We understand that the copy of dependencies (maven/gradle) is important to run because can produce a richer analysis.json, but we think that the code analyzer could print a warning message and let it proceed. So, the only real blocker would be if it couldn’t run Java or other major issues.
Describe alternatives you've considered
This way, the code analyzer would be more robust and we might even support other project structures, like ant.
Metadata
Assignees
Labels
No labels