The (executeworkflow) command line DOES depend on both the engine and common-activities - so they would come all 3 at once in this release candidate - the "command line" only has command line parsing and all the (taverna and external) dependencies in lib/ - it uses taverna-osgi to load all the modules in lib/, then just pokes the engine to run the workflow - then deals with loading and saving of results.
And so any later fix to taverna-osgi, taverna-engine or taverna-common-activities will probably also go hand-in-hand with a new release of taverna-commandline (to update its lib/) - however taverna-osgi have also got online update capability so in theory we don't need to do that so often later. On 26 April 2016 at 17:57, 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
