fix: add group and description to root gradle project for publishing#267
Merged
fix: add group and description to root gradle project for publishing#267
Conversation
tessstoddard
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
This PR adds the group and description back to the root project and then references those values in the
subprojectsblock 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
initializeCentralStagingRepositorytask 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
Checklist: