Java Reference
In-Depth Information
Bundle-Name: jEdit
Bundle-SymbolicName: org.gjt.sp.jedit
Bundle-Version: 4.2
Private-Package:
bsh,
bsh.collection,
bsh.commands,
bsh.reflect,
com.microstar.xml,
gnu.regexp,
installer,
org.gjt.sp.jedit,
org.gjt.sp.jedit.browser,
org.gjt.sp.jedit.buffer,
org.gjt.sp.jedit.gui,
org.gjt.sp.jedit.help,
org.gjt.sp.jedit.icons,
org.gjt.sp.jedit.io,
org.gjt.sp.jedit.menu,
org.gjt.sp.jedit.msg,
org.gjt.sp.jedit.options,
org.gjt.sp.jedit.pluginmgr,
org.gjt.sp.jedit.print,
org.gjt.sp.jedit.proto.jeditresource,
org.gjt.sp.jedit.search,
org.gjt.sp.jedit.syntax,
org.gjt.sp.jedit.textarea,
org.gjt.sp.util,
org.objectweb.asm
Import-Package:
javax.print.attribute,
javax.print.attribute.standard,
javax.swing,
javax.swing.border,
javax.swing.event,
javax.swing.filechooser,
javax.swing.plaf,
javax.swing.plaf.basic,
javax.swing.plaf.metal,
javax.swing.table,
javax.swing.text,
javax.swing.text.html,
javax.swing.tree
Your jEdit bundle doesn't export any packages, but it does use packages from Swing.
These should come from the system bundle, which is typically set up to export
JDK
pack-
ages (although this can be overridden). You may wonder if you should add version
ranges to the packages imported from the
JDK
. This isn't required, because most system
bundles don't version their
JDK
packages. You only need to version these imports if you
want to use another implementation that's different from the stock
JDK
version.
We should also mention that the final manifest contains some bnd-specific head-
ers that aren't used by the
OSG
i framework (such as
Private-Package
,
Tool
, and
Bnd-LastModified
). They're left as a useful record of how bnd built the bundle, but
