handleBuildOperationTypeRaw masks failed build operations about github-dependency-graph-gradle-plugin HOT 3 CLOSED

@leoschweizer better ask the authors, but it looks like there's an npm setup step that needs to happen prior to building the Gradle project.

from github-dependency-graph-gradle-plugin.

Thanks for your detailed report. Yes, the logic here is a bit broken.
I'll get this fixed in an upcoming release.

Gradle's exception handling here is a bit odd ...

If you mean that the failure reported by Gradle lacks the full chain of causes, then yes, Gradle has some special handling to reduce the verbosity of reported failures. If this is the issue, you will likely see all of the causes if you execute with --stacktrace.

I just worked on a fix for a similar issue, where failures to write the dependency graph lacked the underlying cause (unless run with --stacktrace).

from github-dependency-graph-gradle-plugin.

@smowton did you by chance figure out the actual problem with Could not read script '@react-native-community/cli-platform-android/native_modules.gradle' as it does not exist.? I'm seeing the same issue in a react-native project.

from github-dependency-graph-gradle-plugin.