Skip to content

migration from nexus 2 to Central Portal - #1592

Merged
tobixlea merged 2 commits into
aws:mainfrom
tobixlea:sjc-spring-boot-update
Feb 18, 2026
Merged

tobixlea merged 2 commits into
aws:mainfrom
tobixlea:sjc-spring-boot-update

Conversation

@tobixlea

@tobixlea tobixlea commented Feb 18, 2026 •

Copy link
Copy Markdown
Contributor

Issue #, if available:
Nexus 2 is deprecated and publishing through Central Portal is required.
Description of changes:
followed internal migration guide to migrate onto a new repository hosting system called the Central Portal

By submitting this pull request

  • I confirm that my contribution is made under the terms of the Apache 2.0 license.
  • I confirm that I've made a best effort attempt to update all relevant documentation.

@tobixlea
tobixlea merged commit a56f4c6 into aws:main Feb 18, 2026
5 checks passed
ckawl added a commit that referenced this pull request Oct 15, 2026
main moved from Nexus 2 to the Central Portal in #1592. Nexus 2 is retired,
and once a namespace has moved to the Central Portal it must not go back to
OSSRH, so the 2.1.x release workflow cannot be used as it is.

This brings 2.1.x in line with main:
- release.yml is now identical to main's: Central Portal credentials and
  server id, inputs passed through env vars, and the POST that moves the
  staged deployment into the Central Portal for publishing
- pom.xml repositories and distributionManagement point at the OSSRH
  Staging API, as on main
- the archetype poms get a <name>. Maven does not inherit name from the
  parent and the Central Portal rejects a deployment without one, which is
  what main hit in 730906a
ckawl added a commit that referenced this pull request Oct 15, 2026
main moved from Nexus 2 to the Central Portal in #1592. Nexus 2 is retired,
and once a namespace has moved to the Central Portal it must not go back to
OSSRH, so the 1.x release workflow cannot be used as it is.

This brings 1.x in line with main:
- release.yml is main's, except it keeps java-version 8 for the 1.x line.
  That also adds the permissions block main and 2.1.x already have: the
  repository's default token is now read-only, so without contents: write
  the release could not push its commits and tag
- pom.xml repositories and distributionManagement point at the OSSRH
  Staging API, as on main
- the archetype poms get a <name>. Maven does not inherit name from the
  parent and the Central Portal rejects a deployment without one, which is
  what main hit in 730906a
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