Sonatype’s nexus instance (for publishing to Maven Central) has become unusably slow. Specially in this period (possibly caused by the race for java projects to patch log4j vulnerabilities), it can take over 3 hours to close a staging repository, an operation that should normally take under 5 minutes.
They are aware of this and have started adding new projects to a secondary server: https://s01.oss.sonatype.org.
- See their announcement from February 2021 New Users on s01.oss.sonatype.org - The Central Repository Documentation
- See the status page displaying huge delays on the main server, while the secondary server having virtually none: https://status.maven.org/
AFAICS, existing projects can request to be moved to the new server to lighten the load and the Sonatype team seem to be supportive of this. Example of such requests (as jira issues):
So I propose we do the same and create a jira issue requesting to move commons and rendering. We need to provide
- the group ID and
- the list of nexus users allowed to perform operations which will be moved to the new server (and then be allowed to log into it, etc.)
Once this is approved, we need to update the pom.xml to use the new nexus server URL when releasing to Maven Central with the maven nexus plugin.
This is more of an information post, since we’re almost forced to do this due to the current situation, but please feel free to express any ideas you have related to this change.