Repositories include JetBrains Space Compose/dev mirror, causing 503 errors for transitive plugins (e.g., gradle-nexus/publish-plugin) #874

Problem

Several settings.gradle.kts and build.gradle.kts files in this repository include:

maven("https://maven.pkg.jetbrains.space/public/p/compose/dev")

or

maven { url = uri("https://maven.pkg.jetbrains.space/public/p/compose/dev") }

This repository entry is intended for Compose Multiplatform artifacts, but causes problems when used as a generic repository — e.g., if a plugin such as io.github.gradle-nexus:publish-plugin is resolved via this mirror, it may return a 503 error rather than fetching from the correct source.

Example error:

• https://maven.pkg.jetbrains.space/public/p/compose/dev/io/github/gradle-nexus/publish-plugin/2.0.0/publish-plugin-2.0.0.pom returns HTTP 503

Affected files

• build.gradle.kts (root)
• settings.gradle.kts (root)
• samples/compose-resources-gallery/settings.gradle.kts
• samples/ios-cocoapods-static-framework/settings.gradle.kts

Solution

• Only add the JetBrains Space repo in places where Compose artifacts are strictly required.
• For plugins like gradle-nexus/publish-plugin, rely on gradlePluginPortal() or mavenCentral() instead.
• Remove the Space repo as a general-purpose repository to avoid interfering with dependency resolution for unrelated plugins and get rid of HTTP 503 errors.

This report is based on real 503 responses encountered when building downstream projects that depend on moko-resources.

Thanks!