Workaround: Avoid reporting BOMs among dependencies to prevent dependency graphs explosion

[sdedic]

Gradle NB tooling now reports BOMs as regular dependencies and its contents as dependencies. This causes dependency graph explosion as BOMs are used in many intermediate dependencies and the project API explodes the tree eagerly.

For proper function, a change in Dependency API is probably needed, so the client is able to identify BOMs (some flag on output), or exclude them entirely (some additional filter at input) - and to allow lazy creation of dependency tree levels, so that client can avoid the explosion which now happens in project dependency core impl.

For now, it is more safe not to return children of BOMs; it will not affect normal dependencies as BOMs just help to select version of a library.

[lkishalmi]

Looks good. Thanks!