[FELIX-1376] Bundle repository conflict with artifacts when deploying

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: bundlerepository-1.4.0
• Component/s: Bundle Repository (OBR)
• Environment: OS: Windows XP; ; Java(TM) SE Runtime Environment (build 1.6.0_11-b03); Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing)
• Assignee: Unassigned
• Reporter: Santiago Aranda Rojas
• Created: 17/Jul/09 08:23
• Updated: 05/Feb/10 21:10

Description

we are experiencing the following situation when using the bundle
repository 1.4.0 over felix framework 1.8.0.

The scenario is the following:

1) In the remote repository has been published one bundle (org.eclipse.osgi/3.4.0.v20080605-1900 – Equinox) that provide the capability (org.osgi.framework; version 1.4.0)
2) When you try to install a bundle X from the bundles repository that has got a <require> clause to org.osgi.framework; version 1.4.0. The dependency tree is being resolve including a dependency to the Equinox bundle that provides the required capability
3) During the deployment phase, the Equinox bundle is being installed in the Felix framework and a conflict appears due to the that the System
Bundle (Felix framework) exports the same package with the same version

In my opinion, I think that a wrong behaviuor is appearing due to the fact that the bundle repository is not checking if the org.osgi.framework;
version 1.4.0 is exposed and is taking the information from the repository.xml file in order to solve the bundles dependency tree.

Have you checked this behaviour with the bundle repository? Is this experienced behaviour correct according to the dependencies resolution algorithm implemented by the bundle repository?

Issue Links

• is related to: FELIX-280 OBR should be able to confirm satisfaction of a filter, including availability of local resources