| <article link="builders.html"> |
| <title>Project Builders and Natures</title> |
| <date>January 27, 2003</date> |
| |
| <category>Workbench</category> |
| <category>Builders</category> |
| <category>Natures</category> |
| <category>Plug-ins</category> |
| |
| <author> |
| <name>John Arthorne</name> |
| <company>IBM</company> |
| </author> |
| <update> |
| <date>November 23, 2004</date> |
| <author> |
| <name>John Arthorne</name> |
| <company>IBM</company> |
| </author> |
| <reason>for Eclipse 3.0</reason> |
| </update> |
| <description> |
| This article discusses two central mechanisms that are |
| associated with projects in an Eclipse workspace. The first of |
| these is incremental project builders, which create some built |
| state based on the project contents, and then keep that built |
| state synchronized as the project contents change. The second is |
| project natures, which define and manage the association between |
| a given project and a particular plug-in or feature. |
| </description> |
| </article> |