Community
Participate
Working Groups
RFC 174, currently in process, will introduce a new Bundle Collision Hook. The primary purpose of this hook is to provide a way to tell the framework what it should do when encountering a bundle with the same bsn and version. This new hook was necessary because the existing Find Hook could not be used during a bundle update because there is no valid bundle context at that time. The hook implementation will need to filter out any candidate having the same bsn and version as another bundle within the targeted region.
bug348967 is the bug used to implement the Bundle Collision Hook support in the framework. As John points out region digraph will need to be updated to take advantage of the new hook. I suspect we will need to do this in such a way that regions continues to work on an R4.3 Framework which does not have the CollisionHook available.
Should look at doing this for M2.
I released an implementation of the collision hook with commit: http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/?id=620f7deeb1be737dca403e2ae3c84d7a8ebe5752 In order to allow region bundle to continue to run on equinox 3.7 I had to make some changes to use the StandardRegionDigraph internally instead of the RegionDigraph interface. This was to avoid adding a method to get the bundle CollisionHook. Glyn, I felt it was important to you to ensure region continued to run on Equinox 3.7 because I am not sure when Virgo can move up. Plus 3.8 is not releasing until June 2012 so it would mean you would not be able to use the latest region implementation for a long time.
