This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Skip to end of metadata
Go to start of metadata

Release Notes - Apache Taverna Language 0.15.1-incubating and Apache Taverna OSGi 0.2.1-incubating

The Apache Taverna (incubating) team is pleased to announce the release of Apache Taverna Language 0.15.1-incubating and Apache Taverna OSGi 0.2.1-incubating.

This release note is also available at https://s.apache.org/2016-04-12-tavlang

 

This release of Taverna Language is an update that fixes bugs and also adds the Tavlang Tool, contributed by Menaka Madushanka (sponsored by Google Summer of Code 2015).

Taverna Language is available for download from https://taverna.incubator.apache.org/download/language/

 

This release of Taverna OSGi Plugin System will support the upcoming Apache releases of the Taverna EngineTaverna Common Activities, and Taverna Command Line.

Taverna OSGi is available for download from https://taverna.incubator.apache.org/download/osgi/

New Features

Addition of Tavlang Tool to Taverna Language

The Taverna Language command line (tavlang) tool accesses the features of the Taverna language modules. The tool has the following functions:

– Conversion
– Inspection
– Validation
– Viewing workflow statistics.

For more information, see the Apache Taverna Tavlang Tool README: https://s.apache.org/tavlang

Taverna OSGi plugin system

This is the first release of Apache Taverna OSGi plugin system, a plugin system for Java console and desktop applications using OSGi, including an online update mechanism.

For an overview, see the README: https://s.apache.org/taverna-osgi

Improvements/Enhancements

wfdesc export

The module taverna-scufl2-wfdesc is now enabled in the build of Taverna Language.This includes export of workflow structures in RDF Turtle format using the vocabulary http://purl.org/wf4ever/wfdesc

Removed / Retired features

The taverna-scufl2-wfdesc module is no longer runnable as a standalone JAR - this has been superseded by the new tavlang tool.

Bug Fixes

See JIRA change notes:

Apache Taverna Parent: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333249&projectId=12318322

Apache Taverna Language: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333250&projectId=12318322

Apache Taverna OSGi: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332248&projectId=12318322

Known Issues

See JIRA:

Apache Taverna Parent: https://issues.apache.org/jira/browse/TAVERNA/component/12326807

Apache Taverna Language: https://issues.apache.org/jira/browse/TAVERNA/component/12326808

Apache Taverna OSGi: https://issues.apache.org/jira/browse/TAVERNA/component/12326809

Installation Information

Package names have changed to begin with org.apache.taverna and source code has been reorganized.

Prerequisites

Java 1.8 or newer. (Tested with OpenJDK 1.8.)
Apache Maven 3.2.5 or newer. (Older versions will probably work.)

Installation

See Taverna Language download instructions and Taverna OSGi download instructions

More details: http://taverna.incubator.apache.org/  

Stay Informed

Please subscribe to and contact the dev@taverna mailing list for any questions, suggestions, and discussions about Apache Taverna.

Bugs and feature plans are tracked in the JIRA Issue tracker under the TAVERNA components language and osgi. Anyone may add an issue.

Disclaimer

Apache Taverna is an effort undergoing incubation at The Apache Software Foundation (ASF) sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

 

  • No labels

3 Comments

  1. I think we need to make a second draft with the release notes for the engine, as the first vote and release we're doing is just Language and OSGi - and so say the WSDL support note moves there.

    I added links to the JIRA issues fixed - not sure if we want to list them also in here?

  2. I also added descriptions for the JIRA change notes and put them below the TAVERNA-874 bug fix description. I couldn't find the 874 JIRA issue in the change notes; is that correct? Or should it be in the language list?

    I like the JIRA change notes. Are the links permanent? If not, I wonder if we should have the descriptions embedded in the document. Although, there is so much detailed information there, I would prefer to use the links. 

  3. Detailed description of changes:

    1) Reworked intro to match other Apache release notes. Added download links up front.

    2) I changed Removed/Retired Features to NONE.

    3) I changed Known Issues to NONE. (Is this correct?)

    4) I moved TAVERNA-874 to the next release because it's identified as part of the Taverna Commandline.

    5) I added links to the language and osgi download pages.