Team Projects

Most undergraduates and MSc students undertake a team project for which certain shared facilities are required. For each module, students are organised by the module leader into teams of about 7 people. Each team is assigned a moderator, normally a member of staff.

Mailing list

A semi-private mailing list will be created. Members of the team (and possibly the team moderator) will have unrestricted access to the list. Non-members may also post to the list, but will be required to confirm all postings in an attempt to reduce the number of unwanted messages. The postings will be archived for the duration of the project. When posting, please take care to use the list address rather than that of the list maintainer which ends in -request. Messages to the list maintainer that appear to be destined for the list will not be forwarded. You can find out which lists you are subscribed to and hence which team you are a member of by signing on to the University's email list management service with your normal campus ID.

Gitlab repository

A local gitlab version control server is available. All students can create a single repository. Additional resources dedicated to a team project could be created if needed.

Subversion repository

The School subversion server holds a repository for each team. A list of repository names is available from the associated management page.

Configuring Eclipse

You should now be ready to start to configure Eclipse to use its subversion plugin subclipse. These instructions are based on the use of the Linux cluster in The Mill, but a very similar mechanism using Windows and Eclipse from the CS Portable Apps should also work.

  • Start Eclipse and, if necessary, create a new workspace e.g. ~/workspace or H:/workspace.
  • Open "Preferences" on the "Window" menu, then expand "Team" on the left hand side and select "SVN".
    • Make sure Java SVN is set not JavaHL which is the default. This causes it to use an inbuilt java ssh client rather than relying on an external program. There are two references to JavaHL in this dialog. This setting is stored in your profile so is only needed the first time.

At this point you shouild either be able to create a new project and then right click on its top level and select Team->share project .. select SVN type repository ..... or else Import from an existing subversion repository, creating a checked out project as part of the process.

All three URL forms mentioned in should work. The choice is yours - but you should probably avoid saving your campus password as part of your workspace.

Web space

Web space for each team has been created and linked to your team's subversion repository. This web space is not directly updatable other than by checking the content in to your subversion repository. Please note that all content is publicly readable through the file system. The web server that serves these pages has been configured to use PHP so long as you use the .php filename suffix. Each repository has been pre-seeded with a folder called trunk/website. Any content checked in to here is automatically uploaded to your team web space after each commit. It has a URL like:-

This repository can be updated (using TortoiseSVN as the example) as follows:-

  • On a personal machine, install Tortise SVN from (this is already installed in The Rack).

  • Create a new folder for your local copy of the team repository. (See 1 below)

  • Right-click in that new folder and select SVN Checkout. (2)

  • In the window that opens, enter your repository URL. The sample omits the team number (01..26 this year) from the end. You may be asked to authenticate with your normal campus ID. Remember that this starts with a lower case letter. (3)

  • Navigate down to the folder trunk\website. (4)

  • After adding or updating content you will be able to right-click and select "SVN Add" (if needed) and then "SVN Commit". After committing your changes, anything in the website sub-folder is automatically added to your team website within a few seconds.

Using Tortoise SVN


If requested by your module leader, a database will have been created for each team. The username and password for this will be sent to the team members by email, making use of the team mailing list. Please remember that this username and password will probably need to be embedded in scripts or web pages so should not be set to be the same as your campus password.

Direct SQL access to the database is restricted to on-campus hosts - see Databases for details of how a secre tunnel may be opened for remote database administration.