How can I make a case for "dependency management"?
- by C. Ross
I'm currently trying to make a case for adopting dependency management for builds (ala Maven, Ivy, NuGet) and creating an internal repository for shared modules, of which we have over a dozen enterprise wide. What are the primary selling points of this build technique? The ones I have so far:
Eases the process of distributing and importing shared modules, especially version upgrades.
Requires the dependencies of shared modules to be precisely documented.
Removes shared modules from source control, speeding and simplifying checkouts/check ins (when you have applications with 20+ libraries this is a real factor).
Allows more control or awareness of what third party libs are used in your organization.
Are there any selling points that I'm missing? Are there any studies or articles giving improvement metrics?
