| <!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>Build Order</title> |
| |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <H1 CLASS="Head"> |
| Build Order</H1> |
| <P CLASS="Para"> |
| Often the order in which projects are built is important. For |
| example, if one project requires the Java classes which were defined in another |
| project, the first project must be built after its prerequisite classes have |
| been built. The Workbench allows users to explicitly define the order in |
| which projects are built. Alternatively, users can let the platform compute the |
| build order by interpreting project references as prerequisite relationships. |
| The build order is applied for both building the entire workspace or for a group |
| of projects. </P> |
| <P CLASS="Para">You can change this order on the Build Order preferences page. Initially |
| the <b>Use default builder order</b> option is on, in which case the platform computes the |
| build ordering. Turning off this option enables access to the projects list, the |
| ordering of which can be manipulated. Select projects and use the <b>Up</b> and <b>Down</b> |
| buttons to change the build order. Add and remove projects in the build order using the |
| <b>Add Project</b> and <b>Remove Project</b> buttons. Projects removed from |
| the build order <i>will</i> be built, but they will be built after all projects in the build |
| order are built. |
| </P> |
| <P> |
| At the bottom of this page, there is a preference for dealing with build orders that |
| contain cycles. Ideally, you should avoid cyclic references between projects. Projects |
| with cycles really logically belong to a single project, and so they should be collapsed into |
| a single project if possible. However, if you absolutely must have cycles, it may take |
| several iterations of the build order to correctly build everything. Changing this preference |
| will alter the maximum number of times the workbench will attempt to iterate over the build |
| order before giving up. |
| </P> |
| |
| <P>Here is what the Build Order preference page looks like: |
| </P> |
| |
| |
| <P><img src="../images/Image224_pref_build.gif" alt="Build order preference page" border="0" width="616" height="477"> |
| </P> |
| |
| <P><img border="0" src="../images/ngrelr.gif" alt="Related reference" width="159" height="27"> |
| <br><a href="ref-5.htm">Builds</a> |
| <br><a href="ref-59.htm">Project menu</a> |
| </P> |
| |
| <p> <br> |
| <a href="../hglegal2003.htm"><img src = "../images/ngibmcpy2003.gif" alt="Copyright IBM Corporation and others 2000, 2003" border="0" width="324" height="14"></a> |
| </p> |
| |
| </BODY> |
| </HTML> |
