Skip to content

Commit edb2d4d

Browse files
committed
Display nested cause on failure to write dependency-graph file
Gradle provides special handling for certain exception types. We now use `DefaultMultiCauseException` consistently to ensure consistent failure reporting.
1 parent 5cad227 commit edb2d4d

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

plugin/src/main/kotlin/org/gradle/dependencygraph/extractor/DependencyExtractor.kt

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ import org.gradle.dependencygraph.model.*
1212
import org.gradle.dependencygraph.util.*
1313
import org.gradle.initialization.EvaluateSettingsBuildOperationType
1414
import org.gradle.initialization.LoadProjectsBuildOperationType
15+
import org.gradle.internal.exceptions.Contextual
1516
import org.gradle.internal.exceptions.DefaultMultiCauseException
1617
import org.gradle.internal.operations.*
1718
import java.io.File
@@ -311,15 +312,11 @@ abstract class DependencyExtractor :
311312
try {
312313
writeDependencyGraph()
313314
} catch (e: RuntimeException) {
314-
throw GradleException(
315-
"The dependency-graph extractor plugin encountered errors while writing the dependency snapshot json file. " +
316-
"Please report this issue at: https://github.com/gradle/github-dependency-graph-gradle-plugin/issues",
317-
e
318-
)
315+
throw DefaultMultiCauseException("Failed to write dependency-graph to file", e)
319316
}
320317
}
321318

322319
companion object {
323320
private val LOGGER = Logging.getLogger(DependencyExtractor::class.java)
324321
}
325-
}
322+
}

0 commit comments

Comments
 (0)