Using ClassNotFoundException is one way to track them down, but be aware that some such exceptions may not occur until runtime after running successfully for a long time. So, it's a risky approach.
Personally, I can't imagine trying to maintain dependencies without Maven, or an equivalent. I've worked on projects in which jar files were manually saved and moved around - not fun. Not to mention the high overhead on the SCM tool storing all those jar files, and the slowness it creates whenever checking out the repo. And, trying to update versions was a nightmare. With all of that said, the dependency information is in maven and can be extracted from there. Here's another way to get that info -- using the maven central repo web site: http://mvnrepository.com/artifact/org.apache.activemq/activemq-client/5.10.0 Just google "maven repository activemq-client" and that comes right up. -- View this message in context: http://activemq.2283324.n4.nabble.com/What-all-jars-are-required-to-run-ActiveMQ-client-and-what-all-jars-are-included-in-ActiveMq-all-jar-tp4689651p4689736.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
