Skip to content

fix: add group and description to root gradle project for publishing#267

Merged
stevecl5 merged 1 commit intomasterfrom
scl/publishing-fix
Mar 3, 2026
Merged

fix: add group and description to root gradle project for publishing#267
stevecl5 merged 1 commit intomasterfrom
scl/publishing-fix

Conversation

@stevecl5
Copy link
Contributor

@stevecl5 stevecl5 commented Mar 3, 2026

Summary of Changes

As part of the gradle refactor in PR #264, I removed the group and description from the root project and only included them in subprojects. However, the Nexus publishing plugin needs those properties in the root project in order to publish to Maven Central.

This was causing an error during the publishing step of the CI pipeline:

> Task :initializeCentralStagingRepository FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':initializeCentralStagingRepository'.
> Failed to find staging profile for package group: 

This PR adds the group and description back to the root project and then references those values in the subprojects block which should resolve the publishing error.

Public API Additions/Changes

N/A

Downstream Consumer Impact

N/A

How Has This Been Tested?

I verified the Maven Central publishing fix locally by running the initializeCentralStagingRepository task with dummy credentials. The output confirms the Nexus plugin now correctly resolves the root project's package group and bypasses the blank string initialization failure that was breaking the CI pipeline.

Local Publishing Verification Output
path-core % ./gradlew initializeCentralStagingRepository -PossrhUserName=fakeUser -PossrhToken=fakeToken

> Configure project :
Skipping artifact signing for common - missing signing key
Skipping artifact signing for context - missing signing key
Skipping artifact signing for gateway - missing signing key
Skipping artifact signing for gateway-generator - missing signing key
Skipping artifact signing for http - missing signing key
Skipping artifact signing for messaging - missing signing key
Skipping artifact signing for platform - missing signing key
Skipping artifact signing for testing - missing signing key
Skipping artifact signing for utilities - missing signing key

> Task :initializeCentralStagingRepository FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':initializeCentralStagingRepository'.
> Failed to load staging profiles, server at https://ossrh-staging-api.central.sonatype.com/service/local/ responded with status code 401, body: 

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 5s
1 actionable task: 1 executed

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works

@stevecl5 stevecl5 merged commit 8d6656b into master Mar 3, 2026
7 checks passed
@stevecl5 stevecl5 deleted the scl/publishing-fix branch March 3, 2026 22:39
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