Where's the code filling?

Today I was having a problem trying to open a class file I knew the name of but not the project it belonged to (meaning I couldn't just import the package or check it out from CVS). If my workspace hadn't been empty then there wouldn't have been any problem; the Open Type functionality would likely have found the desired class file in the plug-in dependencies. Unfortunately in this case I had just downloaded the nightly build and was using a fresh workspace.

The easiest workaround would have been to create a dummy plug-in project and then try Open Type again. Fortunately, when I mentioned my approach to a co-worker he suggested a more professional solution. His suggestion was to open the plug-ins view, select all the plug-ins in the view, right-click, and select "Add to Java Search." This process created a project in my workspace named External Plug-in Libraries which contained a library of jar files for all the code I might ever want to look at.

In the end, while my co-worker's solution may have been slightly more involved, it definitely seemed like a more proper use of Eclipse functionality and better than my first solution which was just a workaround.