Skip to content

Comments

feat: Migrate from OSSRH to Maven Central Publishing API#68

Open
jmadhur87 wants to merge 2 commits intofortify:masterfrom
jmadhur87:mjain6/migrationToSSCRestapi25.4
Open

feat: Migrate from OSSRH to Maven Central Publishing API#68
jmadhur87 wants to merge 2 commits intofortify:masterfrom
jmadhur87:mjain6/migrationToSSCRestapi25.4

Conversation

@jmadhur87
Copy link

Bump client version from 25.2 -> 25.4
Updated Publishing configuration to publish to Sonatype/Maven Central
Updated CI workflow

Copy link
Contributor

@SangameshV SangameshV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please take care.

- name: Publish to Maven Central
if: github.ref == 'refs/heads/master'
run: ./gradlew publishToOSSRH closeOSSRHStagingRepository
run: ./gradlew publishToSonatype closeAndReleaseSonatypeStagingRepository
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmadhur87 Unless it's somehow required by Gradle plugins, I think it would be more clear to have publishToMavenCentral instead of publishToSonatype Gradle task, and repository mavenCentral instead of sonatype in nexusPublishing section. Other than that, I'm OK with the changes assuming you've tested these, so please go ahead and merge once you've updated sonatype to mavenCentral as described above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants