On multi-module project setups, it is typically preferred to centrally define all repos used by the project in settings.gradle.kts, through the dependencyResolutionManagement block, usually combined with repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS) to enforce that all repos are defined here.
Architectury Loom already supports this behaviour just fine and adds the repositories just fine, but the Architectury Plugin does not perform this check at all and simply just calls project.repositories directly, this causes problems if you're using dependencyResolutionManagement and throws this error when trying to apply the plugin:
An exception occurred applying plugin request [id: 'architectury-plugin']
> Failed to apply plugin 'architectury-plugin'.
> Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by plugin 'architectury-plugin'
On multi-module project setups, it is typically preferred to centrally define all repos used by the project in
settings.gradle.kts, through the dependencyResolutionManagement block, usually combined withrepositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)to enforce that all repos are defined here.Architectury Loom already supports this behaviour just fine and adds the repositories just fine, but the Architectury Plugin does not perform this check at all and simply just calls project.repositories directly, this causes problems if you're using dependencyResolutionManagement and throws this error when trying to apply the plugin: