Skip to main content
Jump to: navigation, search

Difference between revisions of "Plug-in Development Environment"

(Adding 3rd Party Jar files)
Line 26: Line 26:
  
 
Also, eclipse can handle jars within jars.  It expands them into a temporary location during runtime.
 
Also, eclipse can handle jars within jars.  It expands them into a temporary location during runtime.
 +
 +
[[Category:Eclipse Project]]

Revision as of 10:16, 23 April 2007

Plug-in Development Environment (PDE) provides the tools on top of the JDT to develop plugins. It is a part of Eclipse SDK Project.

To debug your plugin you might try the Core Tools

Adding 3rd Party Jar files

Option 1: turn the jars into plug-ins

Use New > Project > Plug-in Development > Plug-in from existing JAR archive. That will turn one or more jar files into a single jar plug-in. For something like log4j you can then set up Buddy-Classloading, etc.

Prior to 3.2.1, you had to make modifications to the build.properties file. See bug 146042 (RCP export has problems with required plug-ins).

Option 2: include the jars in a plug-in

  1. Use Import>File System to import the jar files into your plug-in project, say in the <project>/lib directory.
  2. Use "Add..." to add the jars to the classpath section of the PDE Editor>Runtime tab.
  3. Use "New..." to add "." library back (with no quotes, of course). Some versions of eclipse automatically do this for you.
  4. Make sure your binary build exports the new jar files on the PDE Editor>Build tab.
  5. Save
  6. On the project, use the popup menu>PDE Tools>Update Classpath to correctly add the jars to the eclipse project classpath.
  7. Export any packages that you need to using the PDE Editor>Runtime tab
  8. Save

Check out https://bugs.eclipse.org/bugs/show_bug.cgi?id=108781

It talks about how adding a 3rd party jar removes the default "." classpath, and the need to add it back.

Also, eclipse can handle jars within jars. It expands them into a temporary location during runtime.

Back to the top