Hi! Thanks for showing interest in our project proposal.
I think the idea for the Taverna Language Command Line tool was for it to be separate from the existing Execute Workflow command line tool (the one you have looked at) - although it would be interesting to also consider the new functionality to be part of the command line tool distribution (e.g. as a separate launcher). The Taverna Language module is meant to also be used independently outside Taverna, and therefore has no dependencies on the rest of Taverna. As such it is relatively easier to package and build, and also it does not require the use of the OSGi plugin system that the executeworkflow includes. If you are looking at taverna-comandline for how we did command line options there - be aware that it includes a bit of trickery to work around OSGi threads and classloaders in passing in the command line arguments through the plugin system -- this should not be needed in the proposed Taverna Language command line as it would run with the regular classloader (either with a lib/*.jar collection or as a single executable jar. Note The executeworkflow program might still be slightly in a flux as we have been changing some of the dependencies recently, so it has not yet stabilized after move to Apache. On 7 March 2015 at 15:48, Menaka Madushanka <[email protected]> wrote: > Hi, > I downloaded the taverna language from GIT repository and built it. > And I went through the references that were given in > https://issues.apache.org/jira/browse/COMDEV-120?filter=12330297 > > So, to clarify more about the project I'd like to get some ideas about what > are the command line options that taverna has. > > Also I need to know whether there should be a separate command line > interface. > > Thank you very much. > > Cheers...!!! -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
