Skip to content

repo.eclipse.org - Nexus2 → Nexus3 migration

We’re planning to migrate the Eclipse artifacts repository service (repo.eclipse.org) from Nexus2 to Nexus3 on Thursday, March 12 at 09:00 CET.

Nexus3 brings a number of improvements, including support for multiple repository formats (PyPI, APT, npm, …) and is no longer limited to Maven2.

As part of this migration, we have introduced new repository naming conventions. These changes directly impact existing repository names. To ensure continuity, the old names will remain accessible through URL rewriting. Notable examples include:

  • maven_central → maven-central
  • releases → maven2-releases
  • snapshots → maven2-snapshots

More generally, legacy repositories are following the pattern:

  • <project_short_name>-releases → <project_short_name>-maven2-releases

Example:

  • cbi-release -> cbi-maven2-releases

And for all new repositories creation, the new pattern is as follow:

  • <project_short_name>-<repo_type>-

Example:

  • cbi-npm-releases

NOTE: Deployment rules are also stricter in Nexus3 by default, particularly regarding MIME type validation. For some repositories, this validation had to be disabled to allow successful artifact transfers.

An additional important aspect of this migration relates to supporting the long-term sustainability of the CBI platform. To help achieve this, a storage quota of 50 GB per project has been introduced. This quota is calculated across all repositories belonging to a project, regardless of format (Maven2, PyPI, APT, or others).

All existing artifacts have already been copied to the new platform.

For teams interested in early validation, we would like to invite a limited number of projects to participate in an early validation phase on the new service prior to the official migration date. This would help us observe performance and stability differences with the new version.

This pre-phase will start on March 2nd.

After the migration, if any discrepancies are noticed in the artifacts available on the platform, please do not hesitate to comment on this ticket or open a dedicated ticket so we can investigate and restore.