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 the scope of the Nexus IQ Server, 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, Nexus IQ Server 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.
Terms of Service Privacy Policy
Copyright ©
2008-present, Sonatype Inc. All rights reserved. Includes the
third-party code listed here. Sonatype and Sonatype Nexus are trademarks
of Sonatype, Inc. Apache Maven and Maven are trademarks of the Apache
Software Foundation. M2Eclipse is a trademark of the Eclipse Foundation.
All other trademarks are the property of their respective owners.
Sonatype Headquarters - 8161
Maple Lawn Blvd #250, Fulton, MD 20759
Tysons Office - 8251 Greensboro Drive #610, McLean, VA
22102
Australia Office - 5 Martin Place, Level 14, Sydney 2000, NSW, Australia