update build instructions
diff --git a/README b/README
index 700f8c5..7e069a0 100644
--- a/README
+++ b/README
@@ -9,13 +9,55 @@
Single feature that contains all the jetty jars. That feature is only useful to be able to have tycho publish the jetty-jars.
-Changing version
-----------------
-NEW_VERSION=7.2.0
-mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=$NEW_VERSION-SNAPSHOT
-Then go edit the root pom.xml and change
-<buildnumber>v20101020</buildnumber>
-to the actual qualifier.
+Building
+--------
+Steps:
-Also might need to edit a couple of files manually.
+1. Update the version number
+ Use the set-version.sh script. This accepts an argument of the new version number, eg:
+ > set-version.sh 9.0.3.v20130506
+
+ Alternatively, you can set the variable NEW_VERSION to be the new version number, eg:
+ > export NEW_VERSION=9.0.3.v20130506
+ > set-version.sh
+
+ You can set the variable OLD_VERSION to override the old version number. If you don't set it,
+ then the script will parse the pom.xml to extract the <version> instead. Leaving the OLD_VERSION
+ unset and letting the script determine it is the safest course of action.
+
+
+2. Do the maven/tycho build:
+
+ Here's an example with all options set:
+
+ > mvn -DBRANCH_NAME=jetty-9 -Dset_pom_version=9.0.3.v20130506 -Djetty_release_version=9.0.3.v20130506 -Ddelete_tycho_meta=true -Dforce_context_qualifier= -Dpack_and_sign=true -Dmaven.repo.local=/tmp/jetty-builds/jetty7/localRepo -DforceContextQualifier= -Dpack-and-sign=true -Djetty-release-version=9.0.3.v20130506 clean verify -X -U
+
+
+3. Do the post build:
+
+ > post-tycho.sh
+
+
+Hudson Builds on Eclipse
+------------------------
+
+There are jobs set up on the Hudson instance on build.eclipse.org that will start a build:
+
+ jetty-rt-bundles
+ jetty-rt-bundles-8
+
+
+When using these jobs, you will need to manually start a build. You will be presented with a form asking you to fill in build parameters,
+which are the source of the values you see in Step 2 maven build above.
+
+It is ESSENTIAL that you supply values for the following:
+
+ set_pom_version
+ jetty_release_version
+
+
+Generally, the values for both of these will be identical, ie the latest jetty release number. If you don't provide a value for the set_pom_version,
+then the p2 feature that is generated will default to the values contained in the pom.xml and feature.xml files that were last checked in. For jetty-9
+this is version 9.0.0. set_pom_version controls the version number of the p2 feature, whilst jetty_release_version controls the version number of
+the jetty jars used.
