When using a non-z3 backend (here: the unofficial MOEA backend) that makes a more extensive use of the ExplorationSolution, invalid models can be produced. The reason for this behavior are faulty containment relations since the produced model fragments of the DSE were not contained in any other EObject. Here, it shall be noted that the SuperSets themselves are not intended as containers as of now since they are also used to pass around references to the relevant elements of a DSE.

Furthermore, one warning was produced due to an EAttribute not being set (noticeable on the console).

Technical details:

* getCastedType(...): Used to avoid ugly casting in client code. The DSE language is based on generic IModelElements, whereas the Sets/SuperSets are strict w.r.t. to the types to provide guarantess for the DSE I/O.
* The ExplorationSpecification now contains the the map of input parameters passed to the DSE (Tracing), but not its elements (!).
* ExplorationSolution: 
* * Contains the returned SuperSetMap.
* * Added a "pool" for SuperSets: They are accessible via the SuperSetMap.
* * Added a element "pool" for the generated elements referenced by the returned SuperSets.
* DSMLModelElementFactory: Creating Sets now requires a reference to the SuperSet (reduced code redundancy; can be used for robustness checking later).
* Adapt to the meta-model changes when using SuperSets/Sets (esp in the smt plugin).
refs 3353

refs 2709

refs 3345

refs 2709

Added the treatment of causality constraints for tasks deployed to the same core.
refs 3343

refs 2709

refs 2709

refs 3344

Warning "Restricted access" to be resolved

The exceptions are removed if one presses the Browse button but then press cancel or presses the update button before selecting any file 
refs 3047

The exceptions are removed if one presses the Browse button but then press cancel or presses the update button before selecting any file 
refs 3047

refs 2709

html files and pictures marked as GREEN
refs 3350

pictures added to rating
refs 3350

refs 3350

- Instead, install dispose listener on allocation table editor
refs 2950

- Remember column width when new target elements are added
- Update column sorting when new target elements are added (-> use TreeViewer's column order array instead of actually shuffling the underlying collection of target elements)

Performance improvements
- Avoid full update (i.e., perform more efficient refresh) when names of source or target elements are changed
- Avoid multiple (redundant) updates when editor is opened
- Avoid updating combo boxes when selected element has not changed
- Avoid full update when an allocation is added/removed (simple refresh is enough)
refs 2950

- Remember column width when new target elements are added
- Update column sorting when new target elements are added (-> use TreeViewer's column order array instead of actually shuffling the underlying collection of target elements)

Performance improvements
- Avoid full update (i.e., perform more efficient refresh) when names of source or target elements are changed
- Avoid multiple (redundant) updates when editor is opened
- Avoid updating combo boxes when selected element has not changed
- Avoid full update when an allocation is added/removed (simple refresh is enough)
refs 2950

refs 3346

refs 3346

- ScheduleRun: Generate constraints required for weak causality only for Tasks where only weakly causal Components are mapped
refs 3343

 - AllocationTable.getAllocationTableCollection()
 - AllocationTableCollection.getAllocationTable(Class<T> allocationTableType)
refs 3343

refs 3343

- xmlns:org-fortiss-af3-task="http://www.fortiss.org/af3/task"
- xmlns:org-fortiss-af3-task-allocation="http://www.fortiss.org/af3/task/allocation"

Models will have to be adjusted manually. A migrator is not required since the namespace org-fortiss-af3-task was a assigned twice only after the most recent release (2.12)

refs 2902

refs 2902

No commit message