Optimized Component Lifecycle Management with Sonatype CLM

After reading this chapter, you should be familiar with:

The CLM lifecycle begins with development, and that’s why we believe this is a critical point where developers must have access to information that lets them understand which components they should be using. In the same light, a developers should also be able to see what options are available, and when necessary, be able to communicate the necessity of components that may violate policy.

This approach means that problems are identified and resolved early. Unfortunately, this is in stark contrast with many development models where code is scanned near the end, and a developer is scolded for choices made. Obviously, it’s easy to spot where problems might arise.

Sonatype CLM aims to change this, and the best representation of that is with Sonatype CLM for the IDE.