[flexotask-commits] SF.net SVN: flexotask:[158] trunk/flexotask-update/BUILDCYCLE

[<jsa...@us...>]

Revision: 158
          http://flexotask.svn.sourceforge.net/flexotask/?rev=158&view=rev
Author:   jsauerbach
Date:     2009-06-04 20:53:53 +0000 (Thu, 04 Jun 2009)

Log Message:
-----------
Add an instruction file for how to build a new update site image.  Preparatory to building release 2.0.1 or 2.1.0 or whatever we're going to call it.

Added Paths:
-----------
    trunk/flexotask-update/BUILDCYCLE

Added: trunk/flexotask-update/BUILDCYCLE
===================================================================
--- trunk/flexotask-update/BUILDCYCLE	                        (rev 0)
+++ trunk/flexotask-update/BUILDCYCLE	2009-06-04 20:53:53 UTC (rev 158)
@@ -0,0 +1,30 @@
+This file describes a complete build cycle.  It does not include the instructions for building a vendor's runtime provider
+but includes everything that is under open source control.
+
+1.  Prerequisite:  all Java code builds locally in local projects.   The code tests out using the flexotask-functiontest and
+  flexotask-devtest when run locally.
+
+2.  On a Linux system build the flexotask/native directory using 'make' (see instructions in
+  makefile).
+  
+3.  Build any other components' native directories that are mentioned in 'openRuntime-build.xml' in the flexotask-editor project.
+These include contributions from two tuningforkvp projects: JavaTraceGeneration and JavaTraceGenerationViaNative.
+
+4.  Run openRuntime-build to build the openRuntimeProvider.zip.
+
+5.  In this project (flexotask-update) right-click on site.xml and "Build Site" to build a partial site image.
+
+6.  With a separate utility, run the equinox utility (something like: 
+<path>/eclipse -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -updateSite 
+ <path>/flexotask-update -site file:<path>/flexotask-update/site.xml 
+ -metadataRepositoryName "Flexible Task Graphs Open Source Update Site")
+ 
+7.  The resulting update site has the same shape as a public release on sourceforge.
+
+The actual update site should only be changed by a flexotask project admin.  Special additional steps:
+
+1.  Increment version numbers to ensure a unique identity as seen by the Eclipse update manager.  This must be done
+prior to steps 5-6.
+
+2.  Ensure that the repository is labelled to identify code corresponding to the release (this was not done for version 2.0.0,
+which was a mistake).
\ No newline at end of file


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.