Taverna has now moved to the Apache Software Foundation. For updated information, see Apache Taverna (incubating).

15 Feb /10

Taverna 2.1.1 Patch

A patch for Taverna 2.1 is now available to download.

To install the patch

  1. Start Taverna 2.1. It is best to install the patch when no workflows are being edited or run.
  2. Click “Advanced” on the top menu and select “Updates and plugins”; the Updates and plugins dialog will appear.
  3. Click “Find updates” within the dialog. You should now see that updates are available for three parts of Taverna. You need to install all three updates for Taverna to be patched correctly. Do *not* restart Taverna until all three updates are installed.
  4. Choose “Compatibility” and then click “update” on the right. The Taverna user interface may be unresponsive while the update is downloaded. *Do not quit Taverna*.
    When the update has finished, Taverna will show a dialog warning that the update will not take effect until Taverna is restarted. Do not restart Taverna yet. “Compatibility” should now show that it is version 2.1.1
  5. Update “Services” and then update “Workbench” in a similar manner
  6. Restart Taverna.

Note that the title bar will still say Taverna 2.1.0

The Taverna 2.1.1 Patch includes the following fixes

Credential Manager/Security

The Credential Manager now checks if it is running as a headless process and so decides whether to pop up a password dialog. (T2-698)

The default truststore password on Java 6 Sun Leopard (“changeme”) is now checked for. (T2-1094)

The Credential Manager password dialog is now recognised as a master password provider. (T2-1133)

Beanshell and R services

Beanshell and R prevented users from creating an input and an output port with the same name. This check has been removed. (T2-1127)

Beanshell and R previously allowed users to create ports with invalid names. This is no longer allowed. (T2-1129)

A problem with R services not saving changes to the script was fixed. (T2-1145)


Two concurrency problems were fixed that, in some cases, prevented a large number of iterations over nested workflows running correctly on some Java Virtual Machines (T2-1124 and T2-1137)