Nexus OSS Core has more than 120 REST Resources published. And that number is just increasing with new Nexus Plugins. Not to mention Nexus Pro that comes with even more plugins and more REST resources. Everything you do in Nexus, whether you use the Maven Nexus plugin or the Nexus UI, is interacting with a REST service that is available to you if you want to write your own customizations and scripts. It has been this way since we started the project in 2007. In this post, I’m going to discuss how this came to be, how Nexus was developed with REST in mind from the beginning.
Nexus: A Core of REST Services
When we started the Nexus project, I called it a “blind” application. A “blind” webapp is one with no UI technology whatsoever built-in. All it publishes is a few static files, and a REST API. All of the UI that you see in Nexus is Javascript. Your browser executes Javascript which, in turn, interacts with a set of services. The only presentation technology on the server side is a trivial Velocity template used to render the initial “shell” of the page. Read more…
This video was used as a demonstration reel at January’s Jfokus 2010 in Stockholm, Sweden. It provides a useful walk through of the major features of Nexus Security, including user roles, groups, and privileges. If you are new to Nexus, or if you are evaluating the tool, this five minute video gives you an overview of the UI used to manage Nexus Open Source security.
Highlights of this demonstration of Nexus Security:
When Jason van Zyl and Anders Hammar presented at Jfokus 2010 in Stockholm, Sweden last month, they asked me to put together a demonstration of various core features of Nexus. In this post, we take a look at the demonstration of the Nexus search interface. While this video lacks a soundtrack, they are a good overview of the major features available in the Nexus search interface.
Nexus Professional 1.5.0 ships with a simple branding plugin that makes it easy to add your own logo to the Nexus UI. In this post, you will learn how to install the Nexus Branding Plugin and how to configure Nexus to use your own custom logo.
Step 1: Create a custom logo. If you want to create a drop-in replacement for the default logo, create a 248×50 logo with a transparent background and save it as a PNG. In the video that accompanies this blog post, you’ll see that I have created a 248×50 transparent PNG that has the logo of a fictitious company named “myCorp++”. Read more…
Nicolas Frankel wrote a quick review of Maven: The Complete Reference, and it is positive. Here is his conclusion:
This book is top quality and free: what can I say? If you’re a beginner in Maven, you’ll find a real stable base to learn from. If you need to update your knowledge, you will find a wealth of information. If you’re a Maven guru, please contribute to the Assembly plugin’s chapter. I can only give a warm thank you for Sonatype’s effort for giving this quality book to the community.
Nexus gives you control over the repositories your builds interact with. It can also provide you with an easier way to publish, distribute, and manage the software applications you create. You can get started by downloading Nexus Professional and reading the free Nexus book.
Nexus OSS Core has more than 120 REST Resources published. And that number is just increasing with new Nexus Plugins. Not to mention Nexus Pro that comes with even more plugins and more REST resources. Everything you do in Nexus, whether you use the Maven Nexus plugin or the Nexus UI, is interacting with a REST service that is available to you if you want to write your own customizations and scripts. It has been this way since we started the project in 2007. In this post, I’m going to discuss how this came to be, how Nexus was developed with REST in mind from the beginning.