Jump to: navigation, search

Difference between revisions of "PDE/FAQ"

< PDE
(I have an error that says some package (e.g., com.sun.misc)isn't accessible but it's on my classpath, how do I fix this?)
Line 15: Line 15:
 
= Classpath =
 
= Classpath =
  
== I have an error that says some package (e.g., com.sun.misc)isn't accessible but it's on my classpath, how do I fix this? ==
+
== 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/*'''
 
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/*'''

Revision as of 11:43, 13 July 2009

General

What is PDE

The Plug-in Development Environment (PDE) provides tools to create, develop, test, debug, build and deploy OSGi bundles and RCP applications.

Installation

How do I install PDE?

TODO

Target Management

Classpath

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:

org.osgi.framework.system.packages.extra=com.sun.misc,com.sun.java.swing.plaf.windows

Build

Misc