|
Sounds great.
In the meantime, (and if anyone else is interested)
I've found "DependencyFinder" to be helpful for constructing the list
manually.
-Simon
----- Original Message -----
Sent: Monday, January 22, 2007 9:53
PM
Subject: Re: [orbit-dev] Finding and
Validating Import-Package(s)
The API tool being developed
by Oleg in the PDE incubator should help manifest authors to find those
imports.
In my opinion, the write
thing to add to the wiki is a step to run this tool.
Hi all,
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
import.
In particular I think we should try to be good OSGi citizens and am
looking
to catch non "java.*" packages from the VM so am using
"osgi.compatibility.bootdelegation=false".
So far, I've found a few
misses primarily for xml packages
like:
org.xml.sax,
org.xml.sax.ext,
org.xml.sax.helpers,
org.w3c.dom,
javax.xml.parsers
I
suspect they're missing in other bundles too so it might be worth a
look.
Note: Those packages "usually" come from the system bundle which
is
dependent on the EE, so it might be a good idea to update your manifest
to
have a 1.4 VM at the top, even if your bundle could conceivably be run
on
Foundation 1.0 with separate XML bundles.
--
My real
question is if there's a best practice here that we could put up on
the
wiki..
e.g. What's the best way to find and validate your Import-Package
statements
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 ...?
-Simon
_______________________________________________
orbit-dev mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
|
