Publish artifact to Maven Central #343
Conversation
without releasing the staging repository.
build.gradle.kts
Outdated
| nexusUrl.set(uri("https://s01.oss.sonatype.org/service/local/")) | ||
| snapshotRepositoryUrl.set(uri("https://s01.oss.sonatype.org/content/repositories/snapshots/")) | ||
| username.set(System.getenv("MAVEN_CENTRAL_STAGING_REPO_USER")) | ||
| password.set(System.getenv("MAVEN_CENTRAL_STAGING_REPO_PASSWORD")) |
There was a problem hiding this comment.
It looks like if we set the environment variable names in the right way, this will happen automatically: https://github.com/gradle-nexus/publish-plugin#publishing-to-maven-central-via-sonatype-ossrh
ORG_GRADLE_PROJECT_sonatypeUsername and ORG_GRADLE_PROJECT_sonatypePassword environment variables.
There was a problem hiding this comment.
You are right, seems to work.
@big-guy Yes, I even published all the way to Maven Central: https://search.maven.org/artifact/org.gradle.profiler/gradle-profiler/0.17.0-alpha08/pom Now looking at the pom though, it seems like the packaging is wrong - it says pom. I wonder why. The module file seems to be fine. |
For some reason, the packaging was "pom" for the Gradle profiler artifact.
wolfs
force-pushed
the
wolfs/publish-to-maven-central
branch
from
23f1cf0
to
b2a3717
Compare
|
@big-guy I fixed the packaging attribute and published version 0.17.0-alpha09 to Maven Central. Can you take another look? |
No description provided.