Skip to content

fix: use Njord instead of dead plugin and service#16

Open
cstamas wants to merge 1 commit into
jbangdev:mainfrom
cstamas:use-njord
Open

fix: use Njord instead of dead plugin and service#16
cstamas wants to merge 1 commit into
jbangdev:mainfrom
cstamas:use-njord

Conversation

@cstamas
Copy link
Copy Markdown
Contributor

@cstamas cstamas commented May 24, 2026

OSSRH is gone, and Sonatype CP is the new thing to publish. Use Njord and nothing changes in release process.

Summary by CodeRabbit

  • Chores

    • Updated Maven project metadata and publishing configuration for Central Portal.
    • Replaced prior staging repository settings with Central-style distribution configuration.
    • Integrated Njord-based build/publishing properties and plugin integration into the build.
  • Dependencies

    • Upgraded Groovy integration-test dependency to 4.0.32.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 24, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0c30ed87-d37d-451d-b4c8-2f2e7b1c6301

📥 Commits

Reviewing files that changed from the base of the PR and between 4d868a0 and 1e406d1.

📒 Files selected for processing (1)
  • pom.xml

📝 Walkthrough

Walkthrough

This PR updates pom.xml: adds inceptionYear, replaces SCM and distributionManagement with GitHub and Sonatype Central Portal entries (including snapshot repo), integrates Njord (properties, pluginManagement entry, and build extension), and bumps the integration-test groovy-all dependency.

Changes

Publishing and Build Configuration

Layer / File(s) Summary
Project metadata and publishing repositories
pom.xml
Added inceptionYear and replaced SCM/distributionManagement entries to point to the GitHub repository and Sonatype Central Portal release/snapshot/site URLs.
Njord publishing plugin wiring
pom.xml
Added njord.* properties (version, auto-publish, type, waitForStates), declared the Njord plugin in pluginManagement, and registered eu.maveniverse.maven.njord:extension3 in the build extensions.
Test dependency version update
pom.xml
Updated integration-test org.apache.groovy:groovy-all from 4.0.16 to 4.0.32.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

The rabbit tweaks the pom with care, 🐰
Njord wakes up and starts to share,
Repos align and snapshots fly,
Groovy grows — a newer sky,
A tiny hop, the build takes air.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: replacing the deprecated OSSRH/Nexus publishing setup with Njord for Sonatype Central Portal publishing.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@cstamas cstamas marked this pull request as ready for review May 24, 2026 10:17
OSSRH is gone, and Sonatype CP is the new thing to publish
@cstamas cstamas changed the title Fix: use Njord instead of dead plugin and service fix: use Njord instead of dead plugin and service May 24, 2026
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pom.xml`:
- Around line 49-64: The distributionManagement repository ids don't match the
CI's server id so Maven will fail authentication; update the <id> values under
distributionManagement repository and snapshotRepository from
sonatype-central-portal to ossrh (i.e. change the repository id and
snapshotRepository id to "ossrh") so they match the CI workflow's server-id, or
alternatively update the CI workflow's server-id to "sonatype-central-portal" if
you prefer to keep the current pom; locate the distributionManagement block
(repository, snapshotRepository) to make the change, ensuring the ids align with
the server id used in the CI settings.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7b74f966-f969-4e1d-99d1-f3714baf14e9

📥 Commits

Reviewing files that changed from the base of the PR and between 932742f and 4d868a0.

📒 Files selected for processing (1)
  • pom.xml

Comment thread pom.xml
Comment on lines +49 to +64
<distributionManagement>
<repository>
<id>sonatype-central-portal</id>
<name>Sonatype Central Portal</name>
<url>https://repo.maven.apache.org/maven2/</url>
</repository>
<snapshotRepository>
<id>sonatype-central-portal</id>
<name>Sonatype Central Portal</name>
<url>https://central.sonatype.com/repository/maven-snapshots/</url>
</snapshotRepository>
<site>
<id>github</id>
<url>${project.scm.connection}</url>
</site>
</distributionManagement>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Server ID mismatch will cause deploy authentication failure.

The repository <id>sonatype-central-portal</id> does not match the CI workflow's credential configuration. In .github/workflows/ci.yml:52, credentials are configured with server-id: ossrh. Maven resolves credentials by matching the repository id to the server id in settings.xml—this mismatch means deploy will fail to authenticate.

Either update the repository ids here to ossrh, or update the CI workflow to use server-id: sonatype-central-portal.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pom.xml` around lines 49 - 64, The distributionManagement repository ids
don't match the CI's server id so Maven will fail authentication; update the
<id> values under distributionManagement repository and snapshotRepository from
sonatype-central-portal to ossrh (i.e. change the repository id and
snapshotRepository id to "ossrh") so they match the CI workflow's server-id, or
alternatively update the CI workflow's server-id to "sonatype-central-portal" if
you prefer to keep the current pom; locate the distributionManagement block
(repository, snapshotRepository) to make the change, ensuring the ids align with
the server id used in the CI settings.

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