|
ReleasingVersions
How to use Ant to release the software
Featured IntroductionThis page explains how to release the project software. It only applies if you are a member of the project. The following instructions assume that you are familiar with the terminology of Ant tasks and that you are using Eclipse. Release PolicySoftware should always be released when it is used for demonstration to people other than project members. It is often very useful for us to demonstrate buggy versions. In such cases, it is not necessary to add the release to the downloads section of this site. However, the software should still be jarred up rather than executed straight out of Eclipse. The reason for this is that by jarring up the software, the release mechanism in place ensures that all local changes are committed, thus ensuring that should it be necessary, we are able to revert to the exact version of the software that was used. PrerequisitesThe release mechanism uses the current Subversion revision number. In order to do this, you must have subversion installed locally. Note that this is different to installing Subclipse, the Subversion Eclipse plugin. Releasing from the trunkTypically we have released the software from the trunk of the repository. In order to do this, do the following:
This may fail for a number of reasons, all of which you should pay close attention to and not ignore.
Assuming that all these constraints have been satisfied, you should be able to release the software. The target migensystem-zip creates a directory in My Documents/Software with the name of the release suffixed by the release number. Inside this you will find a zip file. This zip file consists of all the files in that directory (except the zip itself of course). If you want/need to upload the release, this zip file is what you should use. Note that in previous versions of the build.xml, it was possible to specify the version number manually if you didn't have subversion installed. This is no longer supported so as to ensure 100% accurate release information. Releasing from a branchReleasing from a branch is largely very similar to releasing from the trunk. However, you must note the following:
Including additional configs with a release for a study or testAfter you create a release, go to the directory that has been created with the release and:
StandaloneConfigurationFileSource:<name of your file.txt>
|