In the meantime, (and if anyone else is interested)
I've found "DependencyFinder" to be helpful for constructing the list
----- Original Message -----
Sent: Monday, January 22, 2007 9:53
Subject: Re: [orbit-dev] Finding and
The API tool being developed
by Oleg in the PDE incubator should help manifest authors to find those
In my opinion, the write
thing to add to the wiki is a step to run this tool.
I've been trying to validate "Import-Package"s in a few
of the bundles in
Orbit to ensure we didn't accidentally miss a needed
In particular I think we should try to be good OSGi citizens and am
to catch non "java.*" packages from the VM so am using
So far, I've found a few
misses primarily for xml packages
suspect they're missing in other bundles too so it might be worth a
Note: Those packages "usually" come from the system bundle which
dependent on the EE, so it might be a good idea to update your manifest
have a 1.4 VM at the top, even if your bundle could conceivably be run
Foundation 1.0 with separate XML bundles.
question is if there's a best practice here that we could put up on
e.g. What's the best way to find and validate your Import-Package
as doing it manually yourself is error-prone.
Is there a way
to validate an exisiting bundle?
I tried the "create bundle from jar"
wizard (analyze and add dependencies
checked ) from the latest IB however
this added the "exports" but not the
"imports" to the manifest. Is this a
bug or ...?