Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336525 - Installing two equal bundles via the Equinox console places them in different regions
Summary: Installing two equal bundles via the Equinox console places them in different...
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 3.0.0.M01   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: 3.0.0.M01   Edit
Assignee: Glyn Normington CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 10:59 EST by Borislav Kapukaranov CLA
Modified: 2011-02-08 04:42 EST (History)
1 user (show)

See Also:

Attachments
The two test bundles (2.32 KB, application/x-zip-compressed)
2011-02-07 11:01 EST, Borislav Kapukaranov CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Borislav Kapukaranov CLA 2011-02-07 10:59:47 EST 
In a framework hooks built kernel distribution try installing two equal bundles with different filenames via the Equinox console. They both get installed but in different regions.

Steps to reproduce:
1. use the two bundles(in the attached DEV.zip) - they are exactly the same except for the filenames
2. install them sequentially using "install file:<...>"
3. use "ss" and the "vsh bundle list" - the second bundle will be visible in both regions
Comment 1 Borislav Kapukaranov CLA 2011-02-07 11:01:40 EST 
Created attachment 188447 [details]
The two test bundles
Comment 2 Glyn Normington CLA 2011-02-07 11:59:23 EST 
The fix is to remove an unnecessary restriction in the region implementation. This was causing the operation to add the second bundle to the kernel region to fail, leaving the bundle in no region. For some reason, this was then visible in the user region, probably because the vsh code path currently filters out all bundles in the kernel region.

The removed restriction, to avoid bundles with identical symbolic name and version being installed in a region, could not be enforced by the bundle event hook as this cannot fail an install.
Comment 3 Glyn Normington CLA 2011-02-08 04:41:59 EST 
The fix is pushed to the bug330776-framework-hooks branch. Not sure about the target milestone, but let's assume 3.0.0.M01 until proven otherwise.