I've got the reverse problem. Developers keep throwing in jars into the build environment until the project compiles, then they throw in more jars until the project runs. Then over the months as the project evolves and new developers come and go they throw in more jars just to maintain the running project.
Developers rarely go the configuration manager and say please remove these jars they are no longer required.
Often you have a development project that runs with limited resources and nobody has time to analyse which jars are relevant or not. Tools like Jdepend are great but they don't report on secondary classes that are called at runtime after an explicit class call. Apache BCEL looks promising but has no high level interface for the build/run environment.
Can anyone suggest or propose a tool to handle this issue.
A tool called IVY (formerly jayasoft now an Apache project) handles jar dependencies brilliantly and by forcing developers to manage their jar file dependancies through the IVY tool they then tend to take considerably more care in what they introduce into the project.
However IVY doesn't completely solve this problem in its entirity (but sure goes a long way).
