Our projects uses a lot third-party libraries, plus in order to manage the code complexity, we modularize our classes into stand-alone libraries compiled into jars that are then added to various projects as needed.
I'm finding that managing library dependencies in a project is becoming increasingly difficult and cumbersome, especially as the number of in-house libraries keeps creeping up. This is mostly due to the fact, that these libraries are constantly in flux, with new versions being released weekely or even daily. In order too prevent inconsistencies in library use among the team members, every library jar has a datestamp of when it was compiled. This means that when new jars are been released, one has to go into project setup and update the dependencies. This is where the cumbersomeness comes into play.
How do others deal with this issues?
I'm using Maven for packaging and deployment and I really like the way they've solved this problem by using a jar repository and a few other related useful features. Any chance that IDEA may adopt this approach in the future too?