-
Notifications
You must be signed in to change notification settings - Fork 10
Allow analysis.json to be produced even when gradle/gradlew or mvn/mvnw fail to execute #93
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
Comments
I've made some tests using the mvnw and it works test.zip, however, it is failing for this specific test.zip when I am not using the wrapper (You can rename the mvnw to something else, like .mvnw.old or just remove the permission to execute, that is, chmod -x mvnw):
By running Btw, I am using mvn 3.8.4 and Java 21.0.1 |
A new issue was created based on the error above: #95 |
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.
The text was updated successfully, but these errors were encountered: