Skip to content

Gradle plugin incompatible w/centrally declared repositories #847

@rileymichael

Description

@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)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions