Another option is to have a single pair (or a few pairs) of release and snapshot repositories for your entire organization. In this case, the access is controlled by repository targets.
Simply put, a repository target is a way to manage a set of components
based on their paths in a repository. A repository target is simply a
list of regular expressions and a name. For example, a repository target pattern
for Apache Maven would be
./org/apache/maven/. or for Nexus OSS it would be
While it is most common to manage artifacts based on the path of
their groupId, the Regular Expression is matched against the entire
path, and so it is also possible, for example, to define Sources as
In this model, you would create a repository target for each project in your system. You are then able to take the repository target and associate it with one or more repositories or repository groups. This creates new C.R.U.D. privileges specific to the reposiory or group. For example, you could take the Maven repository target, associate it with the release and snapshot repository. You get privileges you can assign to Create, Read, Update, Delete "Maven" (./org/apache/maven/.) artifacts in my Release and Snapshot repositories.
This method is used to manage the http://repository.apache.org instance, where we have just one Release and Snapshot repository and each project team gets permissions to their artifacts based on the path.
First of all, these choices aren’t mutually exclusive. In fact, the
first option builds upon the default repository target of
simply gives you access to all artifacts regardless of the path. You
still associate the default repository target with specific repositories to
create the assignable privileges
In general, it’s my opinion that fewer repositories will scale better and are easier to manage. It’s also easier to start off with a single pair of repositories with the default target and simply refine the permissions as you scale. Most things that are configured per repository (Cache, Storage location, Snapshot purging, etc.) will generally be applicable for all projects, so this mode avoids the duplication of these tasks. Since everything will be stored together in a single folder on disk, it makes backups easier as well.
The reasons why you would want multiple sets of repositories is essentially the opposite of above: If you need different expiration, Snapshot purging, or storage folders, then a single shared repo won’t work. Replication and failover strategies may also make this method easier to support. If you absolutely must maintain total separation between Project teams, i.e. they can’t read each other’s artifacts, then this solution might be more applicable as well.
In summary, Nexus allows you to control the security of your components based on the repository and/or the path of the components, meaning it is possible to slice and dice the system any way you see fit. The default suggestion is to use as few hosted repositories as possible and control the permissions by using repository targets.