I remember seeing an RFC passing by that was containing similar concept,
but I can't recall the number.
Also, the RFC about an API to launch framework was requesting a similar
analysis capability. Note that we had needs similar to the ones captured in
this RFC late last year implemented something in the equinox incubator see
http://wiki.eclipse.org/Equinox_FrameworkAdmin.
PaScaL
"Pernet, Olivier"
<[EMAIL PROTECTED]
p.com> To
Sent by: "OSGi Developer Mail List"
osgi-dev-bounces@ <[email protected]>
www2.osgi.org cc
Subject
07/10/2007 11:22 RE: [osgi-dev] Retrieving a
AM bundle's dependencies
Please respond to
OSGi Developer
Mail List
<[EMAIL PROTECTED]
gi.org>
Thanks a lot ! It seems to be just what I need. It would be nice to have
something like that in the PackageAdmin service though, so that the same
code can be used on all OSGi implementations.
Cheers,
Olivier.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pascal Rapicault
Sent: 10 July 2007 15:35
To: OSGi Developer Mail List
Cc: [email protected]; [EMAIL PROTECTED]
Subject: Re: [osgi-dev] Retrieving a bundle's dependencies
Olivier,
You may want to look at the State API defined in Equinox (see package
org.eclipse.osgi.service.resolver).
It allows to reason about a non-running system and analyze the
dependencies using the information available in the manifest.
It is the main API that PDE tooling as well as the new equinox
provisioning work uses. You can find some helper code and usage of this
API in org.eclipse.pde.build (class PDEState).
HTH,
PaScaL
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
