Very often I inherit code that complains about a class that doesn't exist, and it is just because the jar file is not included in the classpath.
If it's not in the classpath, then you likely don't have the JAR file itself at all. Searching via Eclipse's builtin Ctrl+Shift+T
function won't help much. Usually you can make use of the package name to "guess" where you could get the JAR file from at the internet. E.g. a org.apache.commons.lang.XXX
class is available at http://commons.apache.org/lang.
For the unobvious ones, I myself use http://grepcode.com, the JAR source code search engine.