|[cross-project-issues-dev] Re: [orbit-dev] Goolge Guice (com.google.inject) Bundle in Orbit exports wrong packages versions
We had a similar issue in Galileo with org.eclipse.osgi (Equinox) exporting the wrong version for the org.osgi.util.tracker package. In this case it was only a micro version that was incorrect (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=279622). It was deemed too risky to all of a sudden lower the version of the exported package at the end of the Galileo release. It was even too risky for a point release. Instead we did "fix" it in Galileo SR1 by exporting the package twice (once at the incorrect version and once at the correct version).
In our case it was not so dramatic because there was only a difference between version 1.4.2 and 1.4.0. In your case we are talking about going from package version 2.0 to 1.2. This has far greater semantic differences and I am not sure there is much we can do to fix this at this point. I suggest you consider exporting the package twice (once at the incorrect 2.0 version and once at the correct 1.2 version) in SR1 and allow consumers to migrate to importing the correct version. Then in Indigo you can make the change to drop exporting the 2.0 version. If that proves to be problematic you can always have a compatibility fragment that can be added to export the 2.0 version.
Gunnar Wagenknecht ---06/15/2010 01:01:04 AM---Greetings fellow Orbit committers and Cross-Project readers,
Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
06/15/2010 01:01 AM
[orbit-dev] Goolge Guice (com.google.inject) Bundle in Orbit exports wrong packages versions
Back to the top