An existing application has a ton of JAR files in its classpath. Someone must have added all JARs initially just to be sure. Some of the JARs were obviously not being used and w
Be aware that trial and error alone can be a problem, especially if the application loads classes dynamically (e.g. Class.forName
) as removing a JAR might not prevent the application from starting up and (apparently) work fine, but it may fail later if target classes are not found.
Also, there are many tools that can be used to analyze a Java application and find out dependencies (I have used Dependency Finder myself, although not exactly for this purpose), however note that most of them will also fail to find classes that are loaded dynamically as described above.