| Summary: | Abstract workflow support in MWE2 | ||
|---|---|---|---|
| Product: | [Modeling] EMFT | Reporter: | Natalia Ossipova <mail> |
| Component: | MWE | Assignee: | Project Inbox <emft-mwe-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Build Identifier: MWE lets us define an abstract workflow. An abstract workflow cannot be run directly, it must be called from another workflow passing in the required parameters. Example: <workflow abstract="true"> ... </workflow> <workflow> <cartridge file="${cartrigeFile}" modelFile="${modelFile}" targetDir="${targetDir}" /> </workflow> If the cartridge element has a property "file", it is handled as an inclusion of a graph described in another workflow file. The workflow to be injected doesn't have to have such property. MWE2 should provide support for an abstract workflow definition. Reproducible: Always