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


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

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



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>

* 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>

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


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

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>

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: 3608
Issue-Url: https://af3-developer.fortiss.org/issues/3608



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

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>

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


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

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



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

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

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

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


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

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


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

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


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

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


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

* Refer to the modular JDK-11 in the classpath.
* Depend on openjfx plugins from Tom Schindl.

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


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

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


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

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



Signed-off-by: Marco Volpe <volpe@fortiss.org>

* For a given EClass "Foo", the map considers the generated interface
  class "Foo" and the corresponding implementation class "FooImpl"
  identical.

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



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

* Add new classes
  * MultiValueAnnotationTextEditingSupport, an editing support that
    allows for textual editing of multi-value annotation.
  * MultiValueAnnotationTextEditingDialog, a dialog to that allows to
    edit multiple values
* Adapt
  * EditingSupportFactory to instantiate
    MultiValueAnnotationTextEditingSupport instead of throwning an
    exception about an unsupported case
  * EStructuralFeatureValueProviderBase to set values using the new
    method setAnnotationValueFromString(Collection<String>, T)

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



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

* Editing support: IMultiValueAnnotationEditingSupport with base class
   MultiValueAnnotationEditingSupportBase
    * currently used in MultiValueAnnotationSelectionEditingSupport
    * integrates cell editor (whose updateData() has been dropped in
      favor of the constructor, i.e. a new cell editor is created each
      time
* Dialogs: IMultiValueAnnotationDialog with base class
  MultiValueAnnotationDialogBase
  * currently used by MultiValueAnnotationSelectionDialog

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



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

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

* container.getContainedElements() is of type List<IHierarchicElement>
* The (unchecked) cast of elementRef -> IHierarchicElement has already
  been present in the previous version of this method

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



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

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

Issue-Ref: 3394

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

green

Issue-Ref: 3523
Signed-off-by: Filip Reaboi <reaboi@fortiss.org>

* In the decompose mechanism, the constrained instances are duplicated
  since the resolution of #3293. It is sufficient to remove the
  contrained instances from the container by clearing the list since
  the hierarchical decomposition takes care of the destruction of
  contained specifications.
* Tests: Deleting a component with a test suite succeeds, deleting
  test suites and test suite specs succeeds. The "All tests pass"
  constraint seems to work: It is marked green in a one-component system
  with a "successful" test suite (NOTE: there are currently focus
  problems, so one might need to click into the navigator).

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


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

Signed-off-by: reaboi <reaboi@fortiss.org>

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

YELLOW

Signed-off-by: reaboi <reaboi@fortiss.org>