Community
Participate
Working Groups
Currently the build process uses the director application that is built to provision the different builds. This can be error-prone if there are problems with the director, and ultimately the build will fail miserably. We should modify this process so the director application is only updated at the same frequency as the base-builder. (e.g. only with milestone builds)
The following bundles will need to be added to basebuilder so the director can be run. I assume the ones from 3.4 are sufficient? org.eclipse.core.databinding org.eclipse.core.databinding.beans org.eclipse.equinox.p2.console org.eclipse.equinox.p2.director org.eclipse.equinox.p2.director.app org.eclipse.equinox.p2.engine org.eclipse.equinox.p2.exemplarysetup org.eclipse.equinox.p2.garbagecollector org.eclipse.equinox.p2.touchpoint.eclipse org.eclipse.equinox.p2.touchpoint.natives org.eclipse.equinox.simpleconfigurator org.eclipse.equinox.simpleconfigurator.manipulator org.eclipse.jface org.eclipse.jface.databinding org.eclipse.rcp org.eclipse.ui org.eclipse.ui.workbench org.sat4j.core org.sat4j.pb I'll attach a patch for the remaining changes to the run.xml.
Why do we need JFace/databindings/UI?
I just used all the bundles in the org.eclipse.equinox.p2.director.feature. The ui oriented ones can probably be left out from basebuilder since the build is headless.
Make sure to get the ECF bundles as well.
Yes, the ECF bundles are already there, the new ones I listed are only a delta.
Created attachment 108254 [details] patch test build successful, released for next build.
closing, fixed for N20080723-2000.