This section will be provided in a future version of the document. For now, refer to the Custom Project Wizard Pages design document in bugzilla #90334.
- -8.1 Converting CDT 2.0 Manifest Files
+7.15 Defining Startup Behavior for Configuration Loading
+Tool integrators may require that a plugin contain all the build configurations before projects are loaded. Use of this interface insures that a plugin will have access to build configurations before project inforamation is loaded in the workbench. Two methods can be used to access configuration information just after build definitions have been loaded and then again after the build definitions have been resolved. Added as enhancement to bug 123275.
+++ +public interface IManagedBuildDefinitionsStartup {
+++String BUILD_DEFINITION_STARTUP = "buildDefinitionStartup"; //$NON-NLS-1$
+
+ String CLASS_ATTRIBUTE = "class"; //$NON-NLS-1$
+
+ /**
+ * Any work you want to do on build definitions after they have been loaded but before they have been resolved.
+ */
+ void buildDefsLoaded();
+
+ /**
+ * Any work you want to do on build definitions after they have been resolved.
+ */
+ void buildDefsResolved();}
+
+ + +
The CDT 2.1 Managed Build System (MBS) defined a new object model for tool integrators to use when integrating their tool definitions. The CDT 3.0 model is upward compatible with the CDT 2.1 model with the exception