It talks about how adding a 3rd party jar removes the default "."
classpath, and the need to add it back.
3rd party jar summary:
Option 1: turn the jars into plugins
Use New>Project>Plug-in Development>Plug-in from existing JAR archive.
That will turn one or more jar files into a single jar plugin. For
something like log4j you can then set up Buddy-Classloading, etc.
Option 2: include the jars in a plugin
1. Use Import>File System to import the jar files into your plugin
project, say in the <project>/lib directory.
2. Use "Add..." to add the jars to the classpath section of the
plugin.xml>Runtime tab.
3. Use "New..." to add "." library back (with no quotes, of course).
4. make sure your binary build exports the new jar files on the
plugin.xml>Build tab.
5. save
6. on the project, use context menu>PDE Tools>Update Classpath to
correctly add the jars to the eclipse project classpath.
When you export an Option 2 plugin for deployment, make sure you don't
"Package plug-ins as individual JAR archives" ... eclipse can't load a
jar from within a plugin jar.