Skip to content
Snippets Groups Projects
Select Git revision
  • 4444
  • 4420
  • 4442
  • 4419
  • 4137
  • 4412
  • 4438
  • master default protected
  • 4335
  • 4389
  • 4441
  • 4372
  • 4429
  • 4428
  • 4413
  • 4411
  • 4367
  • 4397
  • 4386
  • 4394
  • 2.26
  • 2.25
  • 2.24
  • 2.22
  • 2.20
  • 2.16
  • 2.14
27 results
Search by author
  • Any Author
  • Andreas Bayha Andreas Bayha bayha
  • Andreea-Diana Folea Andreea-Diana Folea folea
  • Irina Muntean Irina Muntean muntean
  • Konstantin Blaschke Konstantin Blaschke blaschke
  • Moritz Maier ext.m.maier
  • Oluseyi Stephen Adedara adedara
  • Sebastian Bergemann Sebastian Bergemann bergemann
  • Simon Barner Simon Barner barner
  • Tarik Terzimehic Tarik Terzimehic terzimehic
  • Tiziano Munaro Tiziano Munaro munaro
  • Ulrich Schöpp schoepp
11 authors
  1. Dec 20, 2019
  3. Dec 19, 2019
  5. Dec 09, 2019
  7. Nov 14, 2019
  9. Nov 08, 2019
  11. Oct 22, 2019
  13. Oct 18, 2019
  15. Oct 15, 2019
  17. Oct 13, 2019
  19. Oct 10, 2019
  21. Sep 04, 2019
  23. Sep 03, 2019
  25. Sep 02, 2019
  27. Aug 27, 2019
    • Alexander Diewald's avatar
      Import: Fix cyclic loading due to use of wrong save method (now) · b6ccd536
      Alexander Diewald authored 
      * 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: default avatarAlexander Diewald <diewald@fortiss.org>
      b6ccd536
    • Alexander Diewald's avatar
      MigrationService: Reimplement the internal logic · d419ffdd
      Alexander Diewald authored 
      * 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: default avatarAlexander Diewald <diewald@fortiss.org>
      d419ffdd
    • Alexander Diewald's avatar
      Kernel-Services: Move model loading to from init to start phase · 6c64c932
      Alexander Diewald authored 
      * 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: default avatarAlexander Diewald <diewald@fortiss.org>
      6c64c932
  29. Jul 30, 2019
  31. Jul 29, 2019
  33. Jul 26, 2019
  35. Jun 04, 2019
  37. May 07, 2019
  39. May 03, 2019
  41. Apr 03, 2019
  43. Mar 14, 2019
  45. Mar 11, 2019
  47. Mar 08, 2019
  49. Mar 05, 2019
  51. Mar 03, 2019