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.