3818: Avoid NPE in closeEditor()

See merge request af3/kernel!65

Issue-Ref: 3818
Issue-Url: https://af3-developer.fortiss.org/issues/3818


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3818
Issue-Url: https://af3-developer.fortiss.org/issues/3818



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3746
Issue-Url: https://af3-developer.fortiss.org/issues/3746



Signed-off-by: Simon Barner <barner@fortiss.org>

3813: Context menu contributors: Fix class cast exception

See merge request af3/kernel!64

Issue-Ref: 3813
Issue-Url: https://af3-developer.fortiss.org/issues/3813


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* Not all IConnectors are necessarily ILayoutedModelElements

Issue-Ref: 3813
Issue-Url: https://af3-developer.fortiss.org/issues/3813



Signed-off-by: Simon Barner <barner@fortiss.org>

ModelContext: Remove the lastChangeWasIntended state

See merge request af3/kernel!63

Issue-Ref: 3811
Issue-Url: https://af3-developer.fortiss.org/issues/3811



Signed-off-by: Tiziano Munaro <munaro@fortiss.org>

Issue-Ref: 3811
Issue-Url: https://af3-developer.fortiss.org/issues/3811


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Rework migration service

See merge request af3/kernel!62

Issue-Ref: 3806
Issue-Url: https://af3-developer.fortiss.org/issues/3806


Signed-off-by: Florian Hoelzl <hoelzl@fortiss.org>

Issue-Ref: 3806
Issue-Url: https://af3-developer.fortiss.org/issues/3806


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* Replace doSaveAndResetLastChangeWasIntended with the standard doSave
  call to avoid cyclic execution of the runInWorkspace method.
* Regression w.r.t. #2140 does not occur.
* Remove doSaveAndResetLastChangeWasIntended as it is no longer needed.
  It was a workaround anyways.
* Use a non-Dirtying command to execute the migration service. We don't
  want to undo this step.

Issue-Ref: 3806
Issue-Url: https://af3-developer.fortiss.org/issues/3806


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* The service now checks a given input element for the presence of
  migrateable elements if migration providers are queried. By that,
  the registration w.r.t. an element type actually makes sense. Before,
  only the needsMigration(...) method was evaluated.
* Simplify the needsMigration(...) method to indicate whether any
  migration provider applicable for the given input reports the need
  for migration.
* Simplify the migrate(...) logic that will now also report failed
  migrations: the need for migration is checked after the actual
  migration.
* Do not register migrators for ITopLevelElements any more! Instead,
  declare the type that is really relevant for the migration. If you
  need to be launched in every case (avoid that!!!!) one can register
  for FileProject or EObject.

Issue-Ref: 3806
Issue-Url: https://af3-developer.fortiss.org/issues/3806


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* The initialization phase shall ensure that all required information
  about handlers, element types they process etc. are available. It can
  be considered the configuration phase that is later used to process
  instances of elements.
* This change ensures that models are only loaded at the beginning of
  the startup phase such that all services are ready when instances
  of elements shall be processed.
* In particular, this modification will be needed to instantiate all
  missing annotations when a model is loaded to fulfill the respective
  constraint that annotations are always present at model elements for
  whose type they were registered.
* Therefore, a migrator is used. They are executed by a callback from
  the postLoad routine that will also be fired when importing models to
  avoid code duplication. Thus, in order to ensure that the annotation
  service is aware of all present annotations, it must be initialized
  before the model is loaded.
* AF3 startup works as normal and all functionality seems OK. Since this
  is an invasive change under the hood, problems would be noticeable
  immediately, so this one should be fine as no obvious errors could be
  seen.

Issue-Ref: 3746
Issue-Url: https://af3-developer.fortiss.org/issues/3746


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3746
Issue-Url: https://af3-developer.fortiss.org/issues/3746


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3746
Signed-off-by: Alexander Diewald <diewald@fortiss.org>

[3608] Support minimization of energy consumption

See merge request af3/kernel!61

Issue-Ref: 3608
Issue-Url: https://af3-developer.fortiss.org/issues/3608


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Conflicts:
	org.fortiss.tooling.base/src/org/fortiss/tooling/base/utils/.ratings


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

3746

See merge request af3/kernel!60

Issue-Ref: 3746
Issue-Url: https://af3-developer.fortiss.org/issues/3746



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3608
Issue-Url: https://af3-developer.fortiss.org/issues/3608



Signed-off-by: Tiziano Munaro <munaro@fortiss.org>

Issue-Ref: 3746
Issue-Url: https://af3-developer.fortiss.org/issues/3746


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3746
Issue-Url: https://af3-developer.fortiss.org/issues/3746


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

3735: MemoryAreas

See merge request af3/kernel!59

Issue-Ref: 3735
Issue-Url: https://af3-developer.fortiss.org/issues/3735


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3735
Issue-Url: https://af3-developer.fortiss.org/issues/3735



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3735
Issue-Url: https://af3-developer.fortiss.org/issues/3735


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3735
Issue-Url: https://af3-developer.fortiss.org/issues/3735



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3735
Issue-Url: https://af3-developer.fortiss.org/issues/3735



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3735
Issue-Url: https://af3-developer.fortiss.org/issues/3735



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3608
Issue-Url: https://af3-developer.fortiss.org/issues/3608



Signed-off-by: Simon Barner <barner@fortiss.org>

Annotations: Simplify value retrieval

See merge request af3/kernel!57

Issue-Ref: 3750
Signed-off-by: Hernan Ponce de Leon <ponce@fortiss.org>

* The intended way to obtain annotation values by providers requires
  lots of boilerplate code.
* Provide a util method therefore.
* Remove the exception marker for the getAnnotatedValue method as it
  has not been used since ~3 years...

Issue-Ref: 3750
Issue-Url: https://af3-developer.fortiss.org/issues/3750


Signed-off-by: Alexander Diewald <diewald@fortiss.org>