[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[equinox-dev] RE: Looking for a way to verify that all bundles are resolved, from the command line
|
Or would I call the package admin service for that ?
boolean
org.osgi.service.packageadmin.PackageAdmin.resolveBundles(Bundle[]
bundles)
Something like:
packageAdmin.resolveBundles(null);
And check after that which bundles are left unresolved?
--
Cheers
Philippe
philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by Design (tm) - http://www.nexb.com
http://EasyEclipse.org - irc://irc.freenode.net/easyeclipse
> -----Original Message-----
> From: Philippe Ombredanne [mailto:pombredanne@xxxxxxxxx]
> Sent: Tuesday, July 04, 2006 3:46 PM
> To: 'Equinox development mailing list'
> Subject: Looking for a way to verify that all bundles are
> resolved, from the command line
>
>
> Hi,
> I am looking for a way to make a dynamic configuration
> verifications on a bunch of bundles. (That is a distro)
> Ideally I want to have a simple command-line scriptable way
> to resolve all bundles in an eclipse install, and get back
> the output, so we can make that part of our build.
> I played with the console which can start bundles but is not
> scriptable from the command line.
> Is there an available way?
>
> If not, what would be the right approach?
> Would there be a way to get just the resolution going without
> the start?
> Would a snippet like that be all that is need, or is there a
> better way?
>
> Bundle[] bundles =
> MyPlugin.getDefault().getPluginContext().getBundles();
> for (int i = 0; i < bundles.length; i++)
> bundles[i].start();
>
> This would of course be wrapped to handle thrown exceptions
> and error reporting, and made in an application or an ant task.
>
> Thanks for some feedback.
> --
> Cheers
> Philippe
>
> philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
> nexB - Open by Design (tm) - http://www.nexb.com
> http://EasyEclipse.org - irc://irc.freenode.net/easyeclipse
>