Configuration cache report make issue line numbers easier to find even with many issues

[mathjeff]

Expected Behavior

It would be nice if the project isolation issues report generated via ./gradlew help -Dorg.gradle.unsafe.isolated-projects=true would contain a filename and line number for the first few issues that it mentions, even if the number of issues is large

It seems that the reason that stacktraces are missing for many issues is because of a limit on the number of stacktraces here - when I manually increase this number, I start seeing more stacktraces in the report

Some ideas:
A) Perhaps Gradle could always include the first frame of every stacktrace even if there are many stacktraces
B) Perhaps Gradle could reorder the problems in the configuration cache report to show problems with known stacktraces earlier than problems without known stacktraces
C) Perhaps Gradle could offer a property to allow modifying the maximum number of stacktraces
D) Perhaps for issues for which stacktraces aren't known, Gradle could explain how to get the stacktrace

Current Behavior (optional)

Currently when I run ./gradlew help -Dorg.gradle.unsafe.isolated-projects=true I find that most errors list the class that is causing the issue but don't list a line number

This seems to be because there is a limit on the number of stacktraces that will be calculated, set here

Context

I'm trying to address project isolation errors and it's more difficult to know where to look without line numbers

Thanks!

[ljacomet]

This feature request is in the backlog of the relevant team and is prioritized by them.