community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stian Soiland-Reyes (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COMDEV-120) Taverna: Language command line tool
Date Fri, 27 Feb 2015 16:09:05 GMT

     [ https://issues.apache.org/jira/browse/COMDEV-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stian Soiland-Reyes updated COMDEV-120:
---------------------------------------
     Labels: gsoc gsoc2015 java mentor  (was: gsoc gsoc2015 java)
    Summary: Taverna: Language command line tool  (was: GSOC 2015: Taverna Language command
line tool)

> Taverna: Language command line tool
> -----------------------------------
>
>                 Key: COMDEV-120
>                 URL: https://issues.apache.org/jira/browse/COMDEV-120
>             Project: Community Development
>          Issue Type: Bug
>         Environment: Java, Maven
>            Reporter: Stian Soiland-Reyes
>              Labels: gsoc, gsoc2015, java, mentor
>
> Project: Apache Taverna (incubating) http://taverna.incubator.apache.org/
> Mentor: Stian Soiland-Reyes <stain@apache.org>
> Apache Taverna Language - https://github.com/apache/incubator-taverna-language/ - is
a set of Java APIs for managing and converting Taverna workflow definitions.
> Several simple demonstrator/example prototypes for a command line tool over these has
been done, e.g. 
> https://github.com/apache/incubator-taverna-language/tree/master/taverna-scufl2-examples
> https://github.com/apache/incubator-taverna-language/tree/master/taverna-scufl2-wfdesc
> https://github.com/stain/ro-combine-archive
> but what is needed is a single command line tool that is production ready, and ideally
available as an executable standalone jar (As in the wfdesc example).
> This proposed GSOC project is to formalize the command line interface for Taverna Language
so that it can achieve some of the below:
> a) In collaboration with dev@taverna and the mentor, define command line options for
workflow conversions and inspection
> b) Find and use an appropriate command line parser library
> c) --help
> d) Basic error handling (e.g. file not found)
> e) Batch processing - e.g. recursive conversions
> f) Arguments for choosing input and output formats
> g) Unit and Integration Tests for the above (ideally through Maven)
> The project can be extended by exposing other parts of the API that don't currently have
a command line equivalent, e.g.
> h) Workflow validation
> i) Workflow statistics (number of processors, links, etc)
> Your command line tool would be added to the Apache Taverna anguage release, so you would
be a part of the Apache Taverna developer community http://taverna.incubator.apache.org/community/
> which will be able to give feedback, testing and guidance for this GSOC project and beyond.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message