Builders are configured on a per-project basis and run automatically when resources within their project are changed. As such, builders should be fast and scale with respect to the amount of change rather than the number of resources in the project. This typically implies that builders are able to incrementally update their "built state".
The builders extension-point allows builder writers to register their builder implementation under a symbolic name that is then used from within the workspace to find and run builders. The symbolic name is the id of the builder extension. When defining a builder extension, users are encouraged to include a human-readable value for the "name" attribute which identifies their builder and potentially may be presented to users.
<!ELEMENT extension (builder)>
point CDATA #REQUIRED
id CDATA #REQUIRED
name CDATA #IMPLIED>
<!ELEMENT builder (run?)>
hasNature (true | false)
isConfigurable (true | false)
callOnEmptyDelta (true | false)
supportsConfigurations (true | false) >
If the attribute is not specified, it is assumed to be "false".
<!ELEMENT run (parameter*)>
class CDATA #REQUIRED>
<!ELEMENT parameter EMPTY>
name CDATA #REQUIRED
value CDATA #REQUIRED>
<extension id="coolbuilder" name="Cool Builder" point="org.eclipse.core.resources.builders"> <builder hasNature="false"> <run class="com.xyz.builders.Cool"> <parameter name="optimize" value="true"/> <parameter name="comment" value="Produced by the Cool Builder"/> </run> </builder> </extension>If this extension was defined in a plug-in with id "com.xyz.coolplugin", the fully qualified name of this builder would be "com.xyz.coolplugin.coolbuilder".
Copyright (c) 2002, 2010 IBM Corporation and others.
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html