Next you will need to add both of these new repositories to the public Nexus Group. To do this, click on the Repositories link in the left-hand navigation menu in the Views/Repositories section. Nexus lists Groups and Repositories in the same list so click on the public group. After clicking on the public group, you should see the Browse and Configuration tabs in the lower half of the Nexus window.
Note
If you click on a repository or a group in the Repositories list and you do not see the Configuration tab, this is because your Nexus user does not have administrative privileges. To perform the configuration tasks outlined in this chapter, you will need to be logged in as a user with administrative privileges.
Clicking on the Configuration tab will bring up a screen which looks like Figure 4.3, “Adding New Repositories to a Nexus Group”.
To add the two new repositories to the public
Nexus Group, find the repositories in the Available Repositories list on
the right, click on the repository you want to add and drag it to the left
to the Ordered Group Repositories list. Once the repository is in the
Ordered Group Repositories list you can click and drag the repository
within that list to alter the order in which a repository will be searched
for a matching artifact. Once the Google Caja and Google OAuth project
repositories are added to the public Nexus Group, you should be able to
build Apache Shindig and watch Maven download the Caja and OAuth artifacts
from the respective repositories.
Note
Nexus makes use of an interesting Javascript widget library named ExtJS. ExtJS provides for a number of interesting UI widgets that allow for rich interaction like the drag-drop UI for adding repositories to a group and reordering the contents of a group.
In the last few sections, you encountered a situation where you
needed to add two custom repositories to a build in order to download two
libraries (Google Caja and Google OAuth) which are not available in the
Maven Central repository. If you were not using a repository manager, you
would have added these repositories to the repository element of your
project's POM, or you would have asked all of your
developers to modify ~/.m2/settings.xml to reference
two new repositories. Instead, you used the Nexus repository manager to
add the two repositories to the public group. If all of the developers are
configured to point to the public group in Nexus, you can freely swap in
new repositories without asking your developers to change local
configuration, and you've gained a certain amount of control over which
repositories are made available to your development team.
