Nexus Repository 3.0 has hit the streets and continues to spur insightful discussions on where we're headed with the platform. We recently held a one hour demonstration where we had off the chart community engagement with interactive QA. If you missed the demonstration, watch the recording here. What we learned? One hour just wasn't enough. So we took the questions we weren't able to answer, categorized them into topics and published the answers below. We hope you find the information useful. If you have additional questions, leave us a comment and we're happy to continue the discussion. We’ve received quite a few questions on Upgrade from Nexus Repository Manager 2.X to 3.X, and we thought it would be good to aggregate a few of them and describe the process of doing so, as well as what to expect. Can I upgrade from 2.X to 3.X? Will Nexus Repository Manager be unusable while I upgrade? What happens if the Upgrade fails? What prerequisites will there be? How long will it take? When will Upgrade be available? Will I be able to Upgrade everything? Will windows upgrades within Nexus 3.x have a real upgrade path via an installer? Will there be an official Nexus 3 container? Migration supported from existing 2.x to 3.x container? Can Nexus 2 and 3 be run at the same time? Does nexus 3.0 fully support NPM? With support for maven, docker, npm, and bower should this be done on a single server instance of Nexus or would you suggest separating them? How will staging be different in Nexus3? Why the addition of blobs? What are the benefits? Blobstore could use the ability (in UI or Rest) to move artifacts or groups of items from one repo to another. We won't be able to do this on the file system anymore right? Does Nexus deduplicate the data it stores? I.E. upload java 8 JDK to multiple places but it is only stored once. Docker image support esp OpenShift? Is the IQ Server plugin available for IntelliJ now? Does Nexus 3 support manual uploads when nexus is disconnected from internet? When dealing with a "raw" type, would you use the Nexus API to do an automated artifact upload? Or use something like maven deploy-file? Prior versions of Nexus Manager UI have been lacking capability of manually mass-deleting artifacts. You could only delete one artifact at a time. Does the new Nexus 3 UI support mass-selecting and mass-deleting multiple artifacts? Nexus 2 was mainly centered with maven repos. We used to heavily rely on the Artifact upload GUI to upload custom artifacts. We did not see this functionality in Nexus 3.x. Any plan to include it? Will YUM and DEBIAN repositories be supported on windows hosted instances? I understand that Nexus 3 is a big re-write, how much compatibility has been retained for plug-ins, APIs, User Tokens? Can you please comment on ETA when can we expect the re-envisioned Maven repos? Is Nexus Pro 3 out as GA? Will there be functionality added to the Nexus GUI to allow for a "mass" upload (versus the individual component that is available today)? When will nexus 3.X final version be released?
Written by Jeffry Hesse
Jeffry works as a Community Product Owner, where he works to help nurture new and existing contributions to the Sonatype Nexus platform. He writes code with others to give people examples on how to create plugins and contributions for Sonatype products and generally aims to foster a spirit of creativity and contribution in the Open Source community.
Tags
Nuget npm Nexus 3 Docker artifacts Bower Nexus Repository java