The PDE project provides a number of views and editors that make is easier to build plug-ins for Eclipse. Using the PDE, you can create your plug-in manifest file (plugin.xml), specify your plug-in runtime and other required plug-ins, define extension points, including their specific markup, associate XML Schema files with the extension point markup so extensions can be validated, create extensions on other plug-in extension points, etc. The PDE makes integrating plug-ins easy and fun.
PDE also provides comprehensive OSGi tooling, which makes it an ideal environment for component programming, not just Eclipse plug-in development.
PDE is built atop the Platform and JDT, and ships as part of the Eclipse SDK.
The PDE subproject is broken down into two components. Each component operates like a project unto its own, with its own set of committers, bug categories and mailing lists.
| Name | Description |
| Build | PDE Build |
| UI | PDE User Interface |
- PDE Home
- Eclipse PDE Resources
- PDE/Build Development Resources Home
- PDE UI Development Resources Home
- PDE UI Eclipse Wiki
Usefull Resources:
- The Official Eclipse FAQs
- Plugins Version Numbering (Eclipse Wiki)
- FAQ What is the difference between a path and a location?
Newsgroups and Forums
- PDE/Builds Development Newsgroup Archive (Read Only)
- PDE/BUILD Development Official Newsgroup (Require password)
- PDE UI Development Newsgroup Archive (Read Only)
- PDE UI Development Official Newsgroup (Require password)
PDE Tips and Usefull Codes
- How to create a simple Java Project and add various class path, source, plug-in dependency entries. (Code)
- FAQ What is the difference between a path and a location?
