| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| <HTML> |
| <HEAD> |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> |
| <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| |
| <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> |
| <title>Builds</title> |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <H1 CLASS="Head"> |
| Builds</H1> |
| <p CLASS="Head"> |
| A <i>build</i> is a process that derives new resources from existing ones, updates existing resources, or both. </p> |
| <p CLASS="Head"> |
| In the Workbench, different <i>builders</i> are invoked for different types |
| of projects. For example, when a build is triggered for a Java project, a Java |
| builder converts each Java source file (.java files) into one or more executable class files |
| (.class files). Builders usually enforce the constraints of some |
| domain. For example, a Web link builder could update links to files |
| whose name/location changes.</p> |
| |
| <p CLASS="Para" Label="Type">There are two kinds of builds: </p> |
| <ul> |
| <li> |
| <p CLASS="Para" Label="Type">An <i>incremental build</i> leverages a |
| previously built state and applies the transforms of the configured builders |
| to the resources that have changed since the previous state was computed |
| (that is, since the last build).</li> |
| <li> |
| <p CLASS="Para" Label="Type">A full build (or <i>rebuild</i>) discards any |
| previously built state and transforms all requested resources according to |
| the domain rules of the configured builders. The first incremental build is |
| equivalent to a full build as there is no previous state to work from.</li> |
| </ul> |
| <p>Full and incremental builds can be done over a specific set of projects or |
| the workspace as a whole. Specific files and folders cannot be built. There are two ways that builds can be performed:</p> |
| <ul> |
| <li> |
| Automatic builds are performed as resources are saved. Automatic builds are always incremental and always operate |
| over the |
| entire workspace. You can configure your Workbench preferences (<b>Window |
| > Preferences > Workbench</b>) to perform builds automatically on resource |
| modification. </li> |
| <li> |
| Manual builds are initiated when you explicitly select a menu item or press the |
| equivalent shortcut key. Manual builds can be either full or incremental and can operate over collections of projects |
| or the entire workspace.</li> |
| </ul> |
| <p><img border="0" src="../images/ngrelc.gif" alt="Related concepts" width="159" height="27"> |
| <br><a href="concepts-exttools.htm">External tools</a> |
| |
| <p><img border="0" src="../images/ngrelt.gif" alt="Related tasks" width="159" height="27"> |
| <br><a href="../tasks/tasks-73.htm">Building resources</a> |
| <br><a href="../tasks/tasks-75.htm">Performing builds manually</a> |
| <br><a href="../tasks/tasks-16.htm">Performing builds automatically</a> |
| <br><a href="../tasks/tasks-17.htm">Saving resources automatically before a manual build</a><a href="../tasks/tasks-14.htm"><br> |
| Changing build order</a></p> |
| <p><a href="../hglegal2003.htm"><img src="../images/ngibmcpy2003.gif" alt="Copyright IBM Corporation and others 2000, 2003. All Rights Reserved." border="0" width="324" height="14"></a> |
| </p> |
| |
| |
| </BODY> |
| </HTML> |
