You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2016/05/31 23:55:13 UTC
[jira] [Commented] (TAVERNA-973) Support -inputbundle
[ https://issues.apache.org/jira/browse/TAVERNA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308902#comment-15308902 ]
Stian Soiland-Reyes commented on TAVERNA-973:
---------------------------------------------
-inputbundle added for commandline 3.1.0 RC2
Exclusion rules is similar as it was with -inputdoc, e.g. can't be combined with any other -input* parameters.
If an -inputbundle and a -bundle are provided, and they are both the same file, then the bundle will be used "as-is" without any copying. Note that there could be some overwrite issues later if the bundle happens to also already contain an older workflow run - let's find out. :)
> Support -inputbundle
> --------------------
>
> Key: TAVERNA-973
> URL: https://issues.apache.org/jira/browse/TAVERNA-973
> Project: Apache Taverna
> Issue Type: New Feature
> Components: Taverna Command-line Tool
> Reporter: Stian Soiland-Reyes
> Assignee: Stian Soiland-Reyes
> Fix For: command-line 3.1.0
>
>
> It should be straight forward to support a Data Bundle input with a new option {{-inputbundle}} - basically InputsHandler would then just need to copy this file rather than start a new Data bundle.
> Also if {{-bundle}} is provided (for the output bundle), and the file already exits (or the value is the same as the {{-inputbundle}}) - then its inputs should be used directly without any need for copying - but this might require clearing of existing provenance and workflow - so perhaps that's another issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)