Common libraries in a large team

Question

Assume you have five products, and all of them use one or more of the company\'s internal libraries, written by individual developers.

It sounds simple but in practice,

Answer 1

"Duplication is the root of all evil"

Sounds to me like you need:

• An artifact repository like Ivy so you can have the libraries shared and versioned with a distinction between versions that are API stable and ones that are "maturing"
• Tests for the libraries
• Tests for the projects using them
• A continuous integration system so that when an incompatibility or bug is introduced both the project and the original library developer are notified