Question
· Oct 30

Sonatype Nexus as IPM repository?

It's not supported at the moment but is it possible to implement the Sonatype Nexus (or JFrog Artifactory) support based on the current (or upcoming) IPM version?

In repo command help I see there is a support for filesystem repositories (which I have not yet tried) and my current (hopefully not far-fetched) interpretation is the IPM is designed to be able to support different repositories:

zpm:IPMTEST1>help repo
[...]
  ■ Filesystem repository:
    ∙ -filesystem, -f, -fs : Create/update a filesystem repository
    ∙ -depth, -d <value> : For filesystem repositories, specifies the depth (number of folders underneath the root) to search for files named module.xml
    ∙ -path, -p <value> : For filesystem repositories, specifies the path to the root directory
[...]
  ■ Examples
    ∙ repo -name LocalFiles -snapshots 1 -fs -depth 2 -path C:\MyWorkspace\RootModuleDir\
      Create a repository pointing to the filesystem with name LocalFiles, accepting snapshots, looking for files named module.xml up to 2 directories deep in C:\MyWorkspace\RootModuleDir\

The motivation: we already have a repository implementation used for Java and Docker builds and we would like to reuse that instead introducing a new component. I believe we're not the only ones here with this setup.

Discussion (5)4
Log in or sign up to continue

Nexus is not listed in https://oras.land/adopters/ but OCI support is mentioned e.g. here: https://www.sonatype.com/blog/sonatype-nexus-repository-as-a-container-r...

Open Container Initiative (OCI) support

Sonatype Nexus Repository supports the Open Container Initiative
for creating open industry standards on container formats and runtime specifications. This lightweight, open governance structure provides guidance and continued growth across all leaders in the container industry.