Gradle plugin incompatible w/centrally declared repositories

[rileymichael]

Gradle has an incubating feature to declare repositories centrally for all projects via settings.gradle(.kts) instead of in each projects build.gradle(.kts). This was introduced in gradle 6.8.

If a project enables the FAIL_ON_PROJECT_REPOS mode (docs) to enforce this behavior, applying the semanticdb-gradle-plugin will result in a build error as it attempts to configure repos on the project.

Is this repository configuration necessary?

(related to #628 which does not have a conclusion for projects that wish to enforce centrally declared repositories)

[linear]

OSS-24201

[jojosenthusiast]

I'm interested in working on this, but I want to confirm the intended behavior before sending a PR.

Should semanticdb-gradle-plugin avoid configuring project repositories when Gradle central repository management is enabled, or is that repository setup still required for some supported projects? If skipping/guarding that setup is acceptable, I can add a minimal fixture for FAIL_ON_PROJECT_REPOS and keep the change scoped to that path.