From a technical point of view, a software is rarely just a bunch of source code files. By reusing the work of the community, any development team can benefit from very robust and mature libraries while focusing on valuable core business core features. So when code quality matters, dependencies on the community libraries also matters.
- A given version of a library should not be used as this version because it is well known to contain critical bugs
- Need to understand which transitive dependencies can explain why a software depends on a library
- A library should not be used any more as the commercial contract has been broken ended with the company
Two services, Libraries and Dependencies, allows you to cover these use cases.
This service is compatible with:
Navigating through the dependencies of a project is useful. But the ability to work on all projects in order, for instance to know which one depends on library 'dummy' version 'x.y.z' is also very valuable. The Dependencies service allows to do such a thinglets you do that. Starting from the global level, choose the Dependencies option under Tools. You'll then be able to search library usage across projects: