|Mailing List • Forums • IRC|
|Browse Source • Project Set File|
What is PDE
The Plug-in Development Environment (PDE) provides tools to create, develop, test, debug, build and deploy OSGi bundles and RCP applications.
How do I install PDE?
See our Target Definitions page.
How do I find a plug-in (bundle) given a class
If you're interested in finding a class at runtime, please use the PackageAdmin service from OSGi
How do I get access to a plug-in (bundle) in my workspace or target
Use the PluginRegistry API to acquire models from your workspace or target
I have an error that says some package (e.g., com.sun.misc) isn't accessible but it's on my classpath
In most cases, people get this error by accessing the Base64 class from the Sun VM. We generally don't recommend using the Base64 class from the VM because your bundle will be tired to only VMs that have that specific class. However, if this isn't an issue, you can get around the access restriction error by adding an access rule to your system library to make the package accessible. You can do this on the Libraries tab of the Java Build Path project properties. Add an Accessible rule for com/sun/misc/*
Also, in most cases, this package needs to be visible during runtime. To have a package visible during runtime, you will need to add the org.osgi.framework.system.packages.extra system property. For example:
How do I enable API Tooling for my projects
How do I build from SVN
Out of the box, PDE Build does not have the ability to fetch code from a subversion repository. Some discussion have started to make Subversive Fetch tasl part of the BaseBuilder. Subversive provides an SVN fetch task. The corresponding plugin can be downloaded from Subversive's website and some documentation can be found on dedicated wiki page.
Before that, Chris Vines from the community created a plug-in adding this support. It can be found at . Any specific problem with this plug-in must be reported there too.
How do I know if my project is a plug-in project
In PDE, projects have a specific nature (see the .project file) associated with them if they are a plug-in. The PDE nature is:
A typical .project in a plug-in project will look like this:
<?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>org.eclipse.ui.views.log</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.pde.ManifestBuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.pde.SchemaBuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.pde.api.tools.apiAnalysisBuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.pde.PluginNature</nature> <nature>org.eclipse.jdt.core.javanature</nature> <nature>org.eclipse.pde.api.tools.apiAnalysisNature</nature> </natures> </projectDescription>