- 17 Nov, 2017 37 commits
-
-
Andreas Bayha authored -
Johannes Eder authored -
Johannes Eder authored
-
Johannes Eder authored
-
Johannes Eder authored
-
Johannes Eder authored
-
Sudeep Kanav authored
-
Tatiana Chuprina authored
refs 2848
-
Sudeep Kanav authored
-
Simon Barner authoredrefs 2663
-
Johannes Eder authored
-
Johannes Eder authored
-
Johannes Eder authored
-
Johannes Eder authored
-
Johannes Eder authored
-
Simon Barner authored
(with further minor cleanup)
-
Simon Barner authored
(with minor additional refactoring and cleanup)
-
Carmen Carlan authored
refs 3094
-
Carmen Carlan authored
refs 3094
-
Carmen Carlan authored
refs 3094
-
Carmen Carlan authored
refs 3094
-
Simon Barner authored
Use meaningful variable names.
-
Carmen Carlan authored
refs 3094
-
Levi Lucio authored
-
Simon Barner authored
-
Sebastian Voss authored
-
Sebastian Voss authored
-
Simon Barner authored
-
Simon Barner authored
-
Simon Barner authored
-
Sebastian Voss authored
-
Sebastian Voss authored
-
Simon Barner authored
Adjust eOperations of AllocationTable to handle both IUnidirectional and IBidirectional allocations. refs 2950
-
Sebastian Voss authored
-
Sebastian Voss authored
refs 2244
-
Simon Barner authored
Created #3169 to consider splitting of DeploymentUtils after code review. refs 3153
-
Simon Barner authored
A more general approach is required (see #3168). refs 3153
-
- 16 Nov, 2017 3 commits
-
-
Sudeep Kanav authored
refs 3167
-
Sudeep Kanav authored
-
Simon Barner authored
- bidirectional, i.e. if the source(s) can be determined from the target - unidirectional, i.e., if multiple source(s) reference the same target(s) It is mandatory that any concrete AllocationEntrys inherit either IBidirectional or IUnidirectional. TODO: Correctly handle IUnidirectional allocation entries in the getSource/TargetElement[s] eOperations of AllocationTable refs 2950
-