With the release of Nexus Repository Manager OSS 3.0, you might be wondering if it is worth checking out. In my opinion there is no reason not to, since it can be done easily. More importantly, there are lots of reasons to have a look:
01: Installer and archives
Installing the repository is easier than ever before. You can install from archives for the supported operating systems as in the past. Alternatively you can use the new installers that include the required JRE and a setup wizard allowing you to configure paths, ports and service installation.
02: Docker image
If you use Docker to provision your servers, you can include the repository manager now. Just use our official image.
03: REST and Integration API
Once the repository manager is installed you probably want to configure a bunch of users, repositories and perform a few other provisioning tasks. Or you might want to automate these and other tasks for convenient usage at any time. Using the Integration API you can do all that and more.
04: Improved User Interface
The new repository manager version follows modern UI and UX patterns and has a fresh look, while maintaining some familiarity for users of 2.x. It includes wizards and removes obstacles like right-mouse click menus and numerous tabs.
The Nexus Repository Manager has always performed well. With the new release we are topping all our performance metrics and adding new metrics for new repository formats.
06: Docker registries
Docker container images and all their layers constitute even larger binary assets than older use cases like JAR, WAR and EAR files in Maven repositories or other package formats. The benefits of using a repository manager are therefore even larger. Proxying DockerHub and the possibility to run private registries easily, is something Docker users should love in 3.0.
07: npm and bower
08: Raw repositories
We added a bare bones concept of a repository to 3.0 – raw repositories. They are just a bucket of content that you can structure any way you want to host your files. You choose the directories and names and so on. And you can proxy other sites as well. This allows you to use the repository manager to host web pages like a Maven site but also download portals for any files in any structure. Go experiment and tell us how you ended up using them!
09: NuGet repositories
We are not leaving anybody behind – .Net developers get support for NuGet repositories. Proxy the NuGet Gallery and host your own packages.
10: Search Any Component
The repository manager works equally well for all supported repository formats. It supports searching by generic parameters like name and version as well as format specific ones like artifactId. Powered by numerous specific and generic indexes, you will always be able to find the right components, no matter in what repository they are stored.
11: Browse Any Repository
Want an overview of the contents of a repository? Simple, just browse through it and use filters to get a good idea.
12: Health Check Anyone?
Want to know about security and license issues affecting the components in your repositories? We’ve got you covered for Maven, NuGet and npm repositories and there is lots more to come.
So there you have it. There are at least a dozen reasons to start using the 3.0 release. But to be honest, I left the biggest one for last: the new release with all its features and support for numerous formats is freely available as Nexus Repository Manager OSS 3.0!
It’s time to say hello to 3.0. Now, go get it!
Latest posts by Manfred Moser (see all)
- Integration with Nexus Repository 3 - June 8, 2016
- Sonatype Automated Deployments with Atlassian Bitbucket Pipelines - May 24, 2016
- Migrating to Nexus Repository 3 – Easy Peasy - May 11, 2016
- Puppet-eering the Nexus Repository Manager - May 2, 2016
- Impressions from DevOpsDays Vancouver 2016 - April 19, 2016