Eclipse Community Forums: Equinox » Resolving the bundle dependencies dynamically

Help

Home

Home » Eclipse Projects » Equinox » Resolving the bundle dependencies dynamically

Show: Today's Messages :: Show Polls :: Message Navigator

Resolving the bundle dependencies dynamically [message #108504]

Wed, 23 April 2008 13:07

Eclipse User

Originally posted by: Boyan.Yurukov.softwareag.com

Hello,

Does anyone know how I can resolve the dependencies of a bundle before I
start it?

My usecase is that I wish to export a bundle from the framework to another
framework. I need to know which other bundles are required for it to work,
so that I can export them too. What needs to be checked is not only the
required bundles, but also the imported packages, which need to be matched
to the defining bundles.

I could do it by parsing all Manifests of all bundles and sorting out the
links, but if there were a tool or an internal Equinox feature, it would be
much easier.

Greetings,
Boyan.

Report message to a moderator

Re: Resolving the bundle dependencies dynamically [message #108533 is a reply to message #108504]

Wed, 23 April 2008 14:18

Simon Kaegi

Messages: 381
Registered: July 2009

Senior Member

You should take a look at p2.
This is "exactly" what it does.

HTH
-Simon

"Boyan Yurukov" <Boyan.Yurukov@softwareag.com> wrote in message
news:funcbd$7mu$1@build.eclipse.org...
> Hello,
>
> Does anyone know how I can resolve the dependencies of a bundle before I
> start it?
>
> My usecase is that I wish to export a bundle from the framework to another
> framework. I need to know which other bundles are required for it to work,
> so that I can export them too. What needs to be checked is not only the
> required bundles, but also the imported packages, which need to be matched
> to the defining bundles.
>
> I could do it by parsing all Manifests of all bundles and sorting out the
> links, but if there were a tool or an internal Equinox feature, it would
> be much easier.
>
> Greetings,
> Boyan.
>

Report message to a moderator

Re: Resolving the bundle dependencies dynamically [message #108571 is a reply to message #108533]

Wed, 23 April 2008 15:29

Eclipse User

Originally posted by: Boyan.Yurukov.softwareag.com

Thanks, but I actually wrote a simple class that does the same.
http://yurukov.net/sag/eclipse/plugindependency/BundleDepend encyResolver.java
http://yurukov.net/sag/eclipse/plugindependency/plugin_depen dency-example.zip

P2 seems really nice though. I'll try it out later.

Boyan.

"Simon Kaegi" <simon_kaegi@ca.ibm.com> wrote in message
news:funggf$gpl$1@build.eclipse.org...
> You should take a look at p2.
> This is "exactly" what it does.
>
> HTH
> -Simon
>
> "Boyan Yurukov" <Boyan.Yurukov@softwareag.com> wrote in message
> news:funcbd$7mu$1@build.eclipse.org...
>> Hello,
>>
>> Does anyone know how I can resolve the dependencies of a bundle before I
>> start it?
>>
>> My usecase is that I wish to export a bundle from the framework to
>> another framework. I need to know which other bundles are required for it
>> to work, so that I can export them too. What needs to be checked is not
>> only the required bundles, but also the imported packages, which need to
>> be matched to the defining bundles.
>>
>> I could do it by parsing all Manifests of all bundles and sorting out the
>> links, but if there were a tool or an internal Equinox feature, it would
>> be much easier.
>>
>> Greetings,
>> Boyan.
>>
>
>

Report message to a moderator

Previous Topic:	P2: "No repository found at..." for local eclipse installation
Next Topic:	Looking for a speaker to give an Equinox presentation in the Bay Area

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 13:06:48 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter