|[equinox-dev] New Equinox Framework now included in the Equinox and Eclipse Integration builds|
We are well into M1 now for Luna. I thought I would take some time to announce the efforts we have been making to improve the Equinox Core Framework implementation for the Luna release. As you may know from previous posts I have made to the equinox-dev mailing list, we have been working in a branch on significant re-factoring and in many cases rewriting portions of the Equinox Framework. Please see http://wiki.eclipse.org/Equinox/Luna_Framework for more details. The new framework implementation has been in master since the I20130702-1230 integration build.
For most developers this change should not be noticed. But, as documented in the wiki above, there are 4 main areas of concern that the community should be aware of:
1) The Framework no longer uses the old Equinox resolver API org.eclipse.osgi.service.resolver internally to resolve bundles.
2) All Equinox Framework specific hook implementations are broken and will need to migrate. This impacts Virgo and ObjectTeams projects in particular.
3) Removal of Old Style Plugin Support. Compatibility fragment available to add support back.
4) Removal of PlatformAdmin Service Implementation. Compatibility fragment available to add support back.
I actually expect 2) to cause the most heartache, but hopefully for a very small set of developers that need to plug directly into the implementation details of the Equinox framework. For this group of develpers please do not hesitate to direct questions to the equinox-dev mailing list for assistance in migrating to the Luna release.
Please direct any questions or concerns you may have to the equinox-dev mailing list. Also, please give the new framework a try and open any bug reports for issues you come across.
Back to the top