You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2021. It is now read-only.
In project kotlingram I am trying to publish a Kotlin/Multipaltform project that needs Windows, MacOs and Linux, and uses GitHub Actions to do so (see publication_ci.yml).
When executing gradlew publishToSonatype the Nexus Publish Plugin do not use the stagingProfileId set in root project by the Nexus Staging Plugin (see see root build.gradle.kts) and instead creates a new stagin repository with id comgithublamba92-{random_number}. The projects :api:core and :api:bot-builder apply the Nexus Publish Plugin trough the KotlingramPublishedApiPlugin.
Also the Nexus Staging Repository seems to not honor the repository name when creating one with task createRepository, naming the repository with stagingRepositoryId.set(rootProject.name) as well.
This plugin is now deprecated in favor of the new Gradle Nexus Publish Plugin which provides additional tasks to close and release staging repositories. Please refer to the migration guide for details on how to make the switch. If this issue is still relevant to you, please open a new issue in the new repository.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In project kotlingram I am trying to publish a Kotlin/Multipaltform project that needs Windows, MacOs and Linux, and uses GitHub Actions to do so (see
publication_ci.yml
).When executing
gradlew publishToSonatype
the Nexus Publish Plugin do not use thestagingProfileId
set in root project by the Nexus Staging Plugin (see see root build.gradle.kts) and instead creates a new stagin repository with idcomgithublamba92-{random_number}
. The projects:api:core
and:api:bot-builder
apply the Nexus Publish Plugin trough theKotlingramPublishedApiPlugin
.Also the Nexus Staging Repository seems to not honor the repository name when creating one with task
createRepository
, naming the repository withstagingRepositoryId.set(rootProject.name)
as well.Probably related to nexus-staging-plugin/#192
The text was updated successfully, but these errors were encountered: