Community
Participate
Working Groups
Juno milestone releases do not ship org.eclipse.update.core with the classic eclipse anymore so probably it(+ its deps) can be dropped from the bootstrap step. This has to be investigated further.
Chris, would you please investigate this one?
This API may be removed after Juno. http://help.eclipse.org/helios/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fporting%2Fremovals.html But we may have the patch ready earlier.
(In reply to comment #2) > This API may be removed after Juno. > http://help.eclipse.org/helios/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fporting%2Fremovals.html > > But we may have the patch ready earlier. We do have 2 lists of bundles for the first 2 bootstrap steps in the pdebuild.xml. This bug is about removing o.e.update.core(+whatever else is possible) from them. The smaller the bootstrap phase is the easier it is to control it. So the bug is not really dependant on the removal of o.e.update.core from the platform.
PDE Build depends on the mentioned plugins, therefore it cannot be built if bootstrap misses them. I have opened bug 367924 for that.
Created attachment 209062 [details] Work to be retested after PDE Build dependency on update.core is resolved.
On the other hand, we do not need that plugin in bootstrap. Actually, it is not being built anymore for some time, cause it was missing in 4.2 sources, so removing it from bootstrap eclipse.ini (72fcf9a18d3d9e08730b67a677ef55b1332a7b48) is in my opinion enough to close this bug.