The Plug-in Development Environment (PDE) provides tools to create, develop, test, debug, build and deploy Eclipse plug-ins, fragments, features, update sites and RCP products.
PDE also provides comprehensive OSGi tooling, which makes it an ideal environment for component programming, not just Eclipse plug-in development.
In PDE we do tooling, but our business is people!
The PDE subproject is broken down into three main components, Build, UI and API Tools. We also have an Incubator component where we can develop non-SDK features.
|PDE Build||Ant based tools and scripts to automate build processes|
|PDE UI||Models, builders, editors and more to faciliate plug-in development in the Eclipse IDE.|
|PDE API Tools||Eclipse IDE and build process integrated tooling to maintain API|
|PDE Incubator||Development of new tools that are not ready to be added to the Eclipse SDK|
The PDE UI component provides a comprehensive set of tools to create, develop, test, debug and deploy Eclipse plug-ins, fragments, features, update sites and RCP products.
PDE UI also provides comprehensive OSGi tooling, which makes it an ideal environment for component programming, not just Eclipse plug-in development.
Here is a small list of what PDE UI provides to the Eclipse SDK:
The goal of PDE Build is to facilitate the automation of plug-in build processes. Essentially, PDE Build produces Ant scripts based on development-time information provided by, for example, the plugin.xml and build.properties files. The generated Ant scripts, can fetch the relevant projects from a CVS repository, build jars, Javadoc, source zips, put everything together in a format ready to ship and send it out to a remote location (e.g., a local network or a downloads server).
While PDE Build is still being maintained, it is not actively enhanced. For new builds, you can also consider other build systems like Maven Tycho or Gradle.
API tooling will assist developers in API maintenance by reporting API defects such as binary incompatibilities, incorrect plug-in version numbers, missing or incorrect @since tags, and usage of non-API code between plug-ins.
The tooling will be integrated in the Eclipse SDK and will be used in the automated build process.
Specifically, the tooling is designed to do the following:
Back to the top