Community
Participate
Working Groups
See bug 401141 comment 29. org.eclipse.core.runtime.compatibility.registry needs a version increase. We can either touch the bundle or increase its version. I think I will increase the version since we are fixing a real bug in the version that got shipped with Kepler (bug 401098).
Fixed in commit: http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id=a9449e6a50d711231a2f822bd84488cdf8bcd3ce David, are we going to start using the CBI signing solution from bug 401141? If so we will need to bump the version of org.eclipse.core.runtime.compatibility.registry in the 4.3 maint branch.
(In reply to comment #1) > Fixed in commit: > > http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/ > ?id=a9449e6a50d711231a2f822bd84488cdf8bcd3ce > > David, are we going to start using the CBI signing solution from bug 401141? > If so we will need to bump the version of > org.eclipse.core.runtime.compatibility.registry in the 4.3 maint branch. We'll use it in "HEAD" for a while first ... my guess it that it will be at least 2 weeks ... perhaps as long as 2 months ... before we get "settled" (I just say two months, since there's some questions still about signing the executables which might require time/budget to get solved (see bug 388878) and just as well do it all at the same time. I should mention ... so far it is merely my proposal that we do it in maintenance branch too ... should be "PMC approval" that is safe enough, desired, and worth the effort. [Thanks, BTW, for opening those "test failure" bugs].
