Difference between revisions of "STP/Build Component"

From Eclipsepedia

< STP
Jump to: navigation, search
Line 3: Line 3:
 
|-valign="top"  
 
|-valign="top"  
 
|style="width:90%;"|
 
|style="width:90%;"|
'''Work in Progress Here'''
+
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!
The build component contains the top-level build elements for '''all''' components. During a build, the plugins will be compiled, plugin tests will be run, and an update site will be built.
+
 
| align="right | [[Image:Logo_project.gif]]  
 
| align="right | [[Image:Logo_project.gif]]  
 
|}
 
|}
Line 12: Line 11:
 
|-valign="top"  
 
|-valign="top"  
 
|style="width:50%;"|
 
|style="width:50%;"|
<h1>Tasks</h1>
+
<h1>Where's the Source?</h1>
*  Provide SDKs in update site
+
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.
*  Include Ganymede requirements, signing, packing, etc
+
 
  *  Push individual component builds and document these
+
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.
  *  Renovate the download area
+
 
  *  Publish an All-In-One build, with all dependencies
+
* ''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
 +
 
  
<h1>Instructions</h1>
 
* [[STP/Build_Component/Build 101 | Build 101]] - how to do a full build of STP
 
* [[STP/Build_Component/BuildingInTheUI | Build in the UI]] - how to do a full build of STP in your Eclipse IDE
 
* [[STP/Build_Component/Dependencies | Dependencies]] - projects that we need to use for our build
 
 
|}
 
|}
  
 
[[Category:Build]]
 
[[Category:Build]]

Revision as of 20:31, 4 December 2008

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 open Build bugs for inspiration!

Logo project.gif

Where's the Source?

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.