Documentation Nexus IQ Server 1.16

Our documentation site has moved. For the most current version, please see http://help.sonatype.com

7.2. Inheritance

Every organization has rules around component usage. Even if your only rule is, there are no rules, that rule will flow down or out to your development teams. While we will discuss policy in much greater detail in the Policy Management chapter, for now, let’s just consider policy as a representation of all the rules and actions your business has to help identify which components your development teams should be using.

With rules as guidance, your teams will then simply follow that advice and go no further, or they might develop additional rules given very specific needs. Whatever the case, all teams are still accountable for a core set of rules.

In Sonatype CLM, we refer to this flow of policy (rules) as inheritance. In general, whatever is specified for an organization, will extend out to any attached applications.

Of course, Sonatype is flexible enough to allow customization here as well. However, the real advantage to inheritance is when you want to make changes that affect more than one application. If you managed everything at the application level, one change needed for all applications would need to be made to each one. That’s not hard if you have ten applications, but what if you have a hundred, or thousands even?

It is recommended that you manage these pieces at the organization level and allow your applications to inherit those changes.