Menu
Our organization uses Sonatype Nexus to manage artifacts, whether they're internally-hosted stuff we've developed, or proxies to other repositories like Apache or similar. Most stuff is JAR-based.
My group does most of its work in R, and we're wondering whether it makes sense to 1) deploy our internal code as R packages in Nexus, and 2) create a proxy to a CRAN mirror in Nexus. I guess this would take some glue code, but I'm not very cozy with Nexus, so I'm not really sure what that would look like. Ideally it would let us install R packages by hitting Nexus directly, rather than downloading first & manually installing afterwards.
Anyone have suggestions or precedent?
919
Nexus by Sonatype is a repository manager that organizes, stores and distributes artifacts needed for development.
Nexus Vulnerability Scanner OSS Index is a free catalogue of open source components and scanning tools to help developers identify vulnerabilities, understand risk, and keep their software safe.
Yes it supports this.
Since NXRM 3.20.0 support for CRAN is offered in the default install thanks to Sonatype adopting the below mentioned community plugin.
For older NXRM release the Nexus Community has a plugin that adds support for CRAN repositories. You can find it on GitHub to install yourself.
142
Nexus now natively supports R packages as of version 3.20
Check out the release notes: https://help.sonatype.com/repomanager3/formats/r-repositories#RRepositories-RRepositoryGroups
I was able to create R repo's with the same automation.
45
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
