View source for STP/Build Component

__NOTOC__
{|border="0" cellspacing="15" valign="top" style="width:100%;"
|-valign="top" 
|style="width:90%;"|
The Build repository is a separate codebase which includes all of the bits and pieces that we use to run our builds, make update sites, and all that good stuff.  The build materials are managed collectively by the committers to the various components of STP - we're not lucky enough to have a dedicated build team. 

If [[Buckminster]] build systems are something you like, and you think our build could be improved then we really welcome any patches or ideas you may have.  Take a look at the [http://tinyurl.com/5o3jqa open Build bugs] for inspiration!
| align="right | [[Image:Logo_project.gif]] 
|}

{| border="0" cellspacing="15" valign="top" style="width:100%;"

|-valign="top" 
|style="width:50%;"|
<h1>Where's the Source?</h1>
STP uses SVN, and is a multi-repository project, with one repository for each sub-project or component. Individual components can be built (in most cases) independently, but sometimes cross-dependencies exist, and of course a full roll-up build implies access to all the relevant repositories.

SVN repositories can be access through the HTTP protocol, for anonymous read-only checkouts, and the SVN+SSH protocol, for committer checkouts. Here are the repository locations.

* ''BPMN Modeler Project'' :  http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.bpmn-modeler
* ''SCA Tools Project'' :  http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.sca-tools
* ''WS Policy Editor'' :  http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.policy-editor
* ''SOA Intermediate Model'' :  http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.intermediate-model
* ''BPEL 2 Java Framework'' :  http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.bpel2java
* ''Enterprise Integration Designer' :  http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.enterprise-integration
|}

{| border="0" cellspacing="15" valign="top" style="width:100%;"

|-valign="top" 
|style="width:50%;"|
<h1>How Do I Build?</h1>
Once you've checked out the relevant project(s) from SVN in the IDE, the IDE will build it for you, saving all that tedious mucking about with the command line. But if you would like to be able to build it ''headless'' then there are a couple of options. If you have ''shell access'' to the <tt>build.eclipse.org</tt> build infrastructure you can build it there with a minimum of hassle. Note that shell access is only given to committer that have specific responsibilities for builds. If you want to build it on your local machine, you will need to first construct what we call ''the platform'', which is an Eclipse installation with all of the dependencies in place, installed as features and plugins.  The dependencies will change version from milestone to milestone as we head for a roll-up build in the mid-year big-bang release. 

* [[STP/Build/OnEclipseInfrastructure | Builds on the Eclipse build infrastructure]]
* [[STP/Build/BuildOnMyMachine | Builds on your local machine]]

|}

{| border="0" cellspacing="15" valign="top" style="width:100%;"

|-valign="top" 
|style="width:50%;"|
<h1>What about some Useful Links?</h1>
If you are hacking the build, you need to know some things about [[Buckminster]], which is our shield against the slings and arrows of the raw PDE build with its strange Ant script behaviour. [[Buckminster]] is ''relatively'' new, having started up in 2006, but has built a lot of solidity and experience with Eclipse and other projects outside the Eclipse community. Plenty of information is available from the linked wiki page, and I would recommend articles like [[Buckminster/Examples/Building_an_Update_Site | How to Build an Update Site]] to get you going. The guys on the [http://www.eclipse.org/newsportal/thread.php?group=eclipse.tools.buckminster Buckminster newsgroup] and the [http://www.eclipse.org/newsportal/thread.php?group=eclipse.tools.buckminster-dev Buckminster-Dev newsgroup] are usually very responsive too.
|}
[[Category:Build]]