Eclipse Community Forums: Equinox » Using composites to resolve dependencies

Help

Home

Home » Eclipse Projects » Equinox » Using composites to resolve dependencies

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

Using composites to resolve dependencies [message #1824016]

Mon, 06 April 2020 14:41

Sina Madani

Messages: 160
Registered: November 2015
Location: York, UK

Senior Member

Hi,
I was wondering if we are using composites incorrectly for our purposes. Our project depends on bundles available from Orbit, so when the user wants to install our tools from the update site, they also need the Orbit repository (for example, amongst other things), otherwise the install will fail due to missing dependencies. To solve this, we added the Orbit repo as a composite of our own update site . But now we see that this has made the dependent repos list our repo as a composite, causing some issues (see Bug 561805).
How can we get around this? Is this bad design on our part? Or a bug with P2? Is it possible to resolve dependencies in a better way?
Thanks.

[Updated on: Mon, 06 April 2020 15:03]

Report message to a moderator

Re: Using composites to resolve dependencies [message #1824017 is a reply to message #1824016]

Mon, 06 April 2020 14:45

Sina Madani

Messages: 160
Registered: November 2015
Location: York, UK

Senior Member

Searching around, this seems very much related to our issue.

Report message to a moderator

Re: Using composites to resolve dependencies [message #1824046 is a reply to message #1824017]

Tue, 07 April 2020 04:12

Ed Merks

Messages: 33133
Registered: July 2009

Senior Member

Listing something as a child should have no effect on that child nor on any other update site. One consideration with listing something as a child is that each child's content will be available as a choice in the install dialog.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Using composites to resolve dependencies [message #1824068 is a reply to message #1824046]

Tue, 07 April 2020 12:02

Sina Madani

Messages: 160
Registered: November 2015
Location: York, UK

Senior Member

Hi Ed,
Thanks for the reply. I have tried various alternatives, such as using references (the one where there are two identical pieces of information: uri='xxx' and url='xxx', as well as duplicating this with type=1 and type=0) and added the dependency repos to both compositeContent and content.jar (the latter indirectly through feature.xml's <url> <discovery>) but still no dependency resolution occurs. Thus the method outlined in this article doesn't seem to work anymore.

I suppose there isn't a way to hide dependency repositories, and only use them for discovery / resolution of missing features?

Report message to a moderator