Good point - I had a look. > What is the difference between the bundled and standalone executeworkflow
We no longer have a "bundled" command line (which was part of the Taverna Workbench distro), so this title needs to change - more like "What is the difference from the Workbench" Basically the important bit is that you have to do configuration manually. .taverna-cmdline-2.x.x -> .taverna-command-line > The bundled tool will load all the plugins installed for the workbench, > including third-party plugins. However it will also load various > GUI-supporting functions which might consume extra memory. Remove > To install service plugins for the command line tool, one will have to > manually edit the plugins/plugins.xml of the installation or home directory. > The ... block can be copied from the plugins/plugins.xml from the home > directory of a Workbench installation where the plugin is installed. Remove - this needs to be updated with how taverna-osgi installs plugins (which I'm afraid I don't know of the top of my head :)) You can get the updated -help option from running executeworkflow.sh from apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-nightly.zip downloaded from https://builds.apache.org/user/stain/my-views/view/taverna/job/incubator-taverna-commandline-nightly/ws/taverna-commandline-product/target/ There should be a new option for the data bundle output: -bundle <bundle> Save outputs to a new Workflow Run Bundle (zip). On 26 April 2016 at 19:51, Gale Naylor <[email protected]> wrote: > Taverna Commandline Documentation: > > What needs to change in the 2.x documentation? > https://taverna.incubator.apache.org/documentation/command-line/ > If you can bullet-point things that need to change, I'll create a new > webpage for it. Then we can reference this in the README file. > > On Tue, Apr 26, 2016 at 11:08 AM Gale Naylor <[email protected]> > wrote: > >> Regarding the US Export declaration issue: >> If I can summarize what Stian and Ian have said (please correct me if I'm >> wrong), there are two issues. The first issue is that several Taverna >> components use a credential manager that uses the Bouncy Castle encryption >> library. The second issue is we're trying to determine if we also need to >> declare code that uses Apache HTTP Components, Java Secure Socket >> Extension, etc. (See Stian's draft XML doc for the complete possible list - >> see link below.) >> >> If the export restrictions apply, we have to >> (1) Initiate update of www.apache.org/licenses/exports Product >> Classification Matrix.(The Incubator PMC must send the official update >> request.) >> (2) Send a notice to the US Government >> (3) Add a crypto notice to all relevant README files (example: >> http://svn.apache.org/repos/asf/httpd/httpd/trunk/README) >> >> More info: >> ASF Export info: http://www.apache.org/licenses/exports/#embargoed >> JIRA issue: https://issues.apache.org/jira/browse/TAVERNA-959 >> Question for Legal: https://issues.apache.org/jira/browse/LEGAL-250 >> Draft Taverna Export XML: >> https://cwiki.apache.org/confluence/display/TAVERNADEV/Taverna+Crypto+draft+XML >> Reporting requirements: http://www.apache.org/dev/crypto.html >> >> On Tue, Apr 26, 2016 at 9:57 AM Gale Naylor <[email protected]> >> wrote: >> >>> Regarding release order: I was just curious. It sounds logical to release >>> the command line first since it would be helpful for the GSOC students and >>> doesn't depend on taverna-engine or taverna-common-activities. >>> >>> On Tue, Apr 26, 2016 at 9:30 AM Alan Williams <[email protected]> >>> wrote: >>> >>>> On 26-Apr-16 17:05, Stian Soiland-Reyes wrote: >>>> > We can do taverna-engine and taverna-common-activities separately if >>>> > that makes sense.. I was thinking that we don't really know they work >>>> > until used in the command line and the command line would be useful >>>> > for the GSOC students (e.g. particularly for the Docker activity) - >>>> > but I'm open to either. If we don't do the >>>> > >>>> > I was thinking of preparing the release candidate this week - but I >>>> > think rather wait until early May so we get that US Export declaration >>>> > sorted first. >>>> >>>> Can you give a brief summary of the "US Export declaration" issue? >>>> >>>> Alan >>>> >>>> >>>> -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
