Migrate to publishing Maven Central from Sonatype URLs

[DavidWhitlock]

I got this note from the Maven Central folks:

NOTE: If you have already migrated your namespace(s) to Maven Central this email does not apply to you and thank you for your initiative.

Greetings OSSRH Publisher,

As you may have heard, OSSRH is reaching end of life on June 30, 2025. OSSRH users need to migrate their namespaces to the Central Portal as soon as possible.

Instructions for self migration are located here: https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#self-service-migration

To make the transition smoother we will be automatically migrating publishers that have not used oss.sonatype.org or s01.sonatype.org to publish artifacts in some time starting with the oldest and working our way forward. To avoid disruption to your publishing processes we strongly encourage migrating before the June 30, 2025 deadline.

Thank you for your assistance,

The Central Team

The project still uses the Sonatype URL for the snapshot repository. I need to figure out what to do here.

[DavidWhitlock]

It looks like the details of configuring the pom.xml can be found here: https://central.sonatype.org/publish/publish-portal-maven/

And here's how to work with SNAPSHOT artifacts: https://central.sonatype.org/publish/publish-portal-snapshots/

[DavidWhitlock]

Cool. It looks like additional information is necessary in the pom.xml:

Deployment f9cb06b9-68aa-4037-81d7-8aa16a8e0d97 failed
pkg:maven/io.github.davidwhitlock.joy/web@2.0.0:
 - Developers information is missing
 - License information is missing
 - Project description is missing
 - SCM URL is not defined

pkg:maven/io.github.davidwhitlock.joy/web@2.0.0?type=war:
 - Component with package url: 'pkg:maven/io.github.davidwhitlock.joy/web@2.0.0?type=war' already exists

Oh. I bet that information is only needed on production (non-SNAPSHOT) versions. I just happen to catch it because the web POM hadn't had its version updated to a SNAPSHOT version.

[DavidWhitlock]

I've encountered a couple of problems (500 errors) while uploading artifacts to the Maven Central Snapshots.

And attempting to browse the repository indicates that there is a problem in the repository:

https://central.sonatype.com/service/rest/repository/browse/maven-snapshots/io/github/davidwhitlock/joy/family/1.1.4-SNAPSHOT/

ERROR: (ID 28abb6f0-1ed2-4891-8bb8-cece90ef7279) org.sonatype.nexus.datastore.api.DataAccessException: 
### Error querying database.  Cause: org.postgresql.util.PSQLException: ERROR: out of memory
  Detail: Failed on request of size 147504.
  Where: parallel worker
### The error may exist in org.sonatype.nexus.content.maven.internal.browse.Maven2BrowseNodeDAO
### The error may involve defaultParameterMap
### The error occurred while setting parameters
### SQL: SELECT B.*,         CASE WHEN C.last_updated IS NULL THEN A.last_updated ELSE C.last_updated END AS last_updated,         NOT EXISTS (      SELECT 1 FROM maven2_browse_node C WHERE C.repository_id = ? AND C.parent_id = B.node_id LIMIT 1    ) as leaf FROM                    maven2_browse_node B0,                    maven2_browse_node B1,                    maven2_browse_node B2,                    maven2_browse_node B3,                    maven2_browse_node B4,                    maven2_browse_node B5,                   maven2_browse_node B     LEFT JOIN maven2_component C ON B.component_id = C.component_id     LEFT JOIN maven2_asset A ON B.asset_id = A.asset_id     WHERE 0 =                  B0.parent_id AND B0.repository_id = ? AND B0.display_name = ? AND B0.node_id =                                B1.parent_id AND B1.repository_id = ? AND B1.display_name = ? AND B1.node_id =                                B2.parent_id AND B2.repository_id = ? AND B2.display_name = ? AND B2.node_id =                                B3.parent_id AND B3.repository_id = ? AND B3.display_name = ? AND B3.node_id =                                B4.parent_id AND B4.repository_id = ? AND B4.display_name = ? AND B4.node_id =                                B5.parent_id AND B5.repository_id = ? AND B5.display_name = ? AND B5.node_id =                               B.parent_id AND B.repository_id = ?                     LIMIT ? ;
### Cause: org.postgresql.util.PSQLException: ERROR: out of memory
  Detail: Failed on request of size 147504.
  Where: parallel worker

I'll try again later when the Maven repo is healthier.