This is part of the Tutorial - Checking out Taverna source code, compiling, running and debugging

• Tutorial overview: Tutorial - Checking out Taverna source code, compiling, running and debugging
• Next step: 2. Configuring Maven

Outdated This page is outdated and might refer to SVN repositories at Google Code. Apache Taverna 3 source code is available at http://taverna.incubator.apache.org/download/code/ Taverna 2 source code is available at https://github.com/taverna/

Introduction

We assume you have already configured Eclipse with the Subversive and m2eclipse plugins installed as described in Prerequisites.

Browse the repository

Start Eclipse from a new workspace, as checking out Taverna will add multiple projects. We'll show later how to group these using Working Sets. In order to avoid Maven conflicts with any projects you already have open, we initially recommend you to check out Taverna using a separate workspace.

From Eclipse's menu, do File -> Switch Workspace -> Other...  and select a new, non-existing folder (that is not inside another Eclipse workspace), like /home/stain/src/taverna-workspace.

Next, we're going to add and browse the Subversion repository from where we'll find Taverna.

In Eclipse, click Window->Open perspective..->Other and select SVN Repository Exploring.

On the left hand side in the new perspective, Either click the New Repository Location button  , or right-click in the white space and select New -> Repository location..

Set the URL to http://taverna.googlecode.com/svn/taverna and click Finish.

Write access If you have been granted Subversion write access - use https instead of http above, and fill in your username as johndoe@mygrid.org.uk and the generated Subversion password as shown on Google Code.

You should see a tree similar to the one below:

Browsing the root As all of the source code for Taverna Workbench is located below /taverna we added the repository including this folder, but you may also browse the rest of the repository expanding the folder link ROOT.

Checking out the source code 

Expand builds and taverna-workbench to reveal the trunk/branches/tags structure for the build project, and expand branches.

Right-click on maintenance and select Check out. An Operation in progress dialogue should appear, and might take several minutes to complete depending on your network connection.

SVN externals If you browse the folders within builds/taverna-workbench/branches/maintenance you'll notice that there's almost no source code. This is because the individual modules of Taverna are maintained in separate folders in the Subversion repository, which are fetched as part of your checkout using SVN external definitions on the folders like engine, so that builds/taverna-workbench/branches/maintenance/engine/net.sf.taverna.t2.core is actually checked out from engine/net.sf.taverna.t2.core/branches/maintenance

Once Taverna has been checked out, Eclipse should change to the Java perspective and show you the build project taverna-workbench. To confirm that the individual modules have been checked out, you may expand the folders like utils to check that they contain subfolders like net.sf.taverna.t2.lang. (Except the parent folder which only contains pom.xml).

Next in this tutorial we'll configure Maven - you may proceed to the next tutorial step before the checkout has completed by clicking Run in background.

Which version to check out?

This tutorial checks out the maintenance branch, assuming you want to check out the source code for the next release of the Taverna Workbench (at the time of writing that will be Taverna 2.3).

Maintenance branch The maintenance branch was introduced after the release of Taverna 2.2 for the preparation of the next release of the workbench (2.3), while the trunk is being refactored to use the plugin system OSGi. The work on moving to OSGi will initially focus on the workflow engine, so at the time of writing, the trunk can't run the workbench.

If you still would like to look at the latest, bleeding edge source code, you can check out the trunk. Note that at the time of writing, the trunk code does not produce a running workbench.

If you want to mainly look at the source code for an already released version of Taverna, check out the tag for the version, for example tags/taverna-workbench-2.2.0:

In this case it would generally be easier and faster to download the source code zip file of the release and import the code tree to Eclipse. Older source code releases are available from LaunchPad.

• Tutorial overview: Tutorial - Checking out Taverna source code
• Next step: 2. Configuring Maven