1. 29 Apr, 2020 1 commit
  2. 16 Apr, 2020 1 commit
  3. 15 Apr, 2020 1 commit
  4. 09 Apr, 2020 1 commit
  5. 03 Mar, 2020 1 commit
  6. 18 Feb, 2020 1 commit
  7. 20 Dec, 2019 1 commit
  8. 19 Dec, 2019 2 commits
  9. 09 Dec, 2019 3 commits
  10. 03 Sep, 2019 1 commit
  11. 02 Sep, 2019 1 commit
  12. 27 Aug, 2019 3 commits
    • 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: Alexander Diewald's 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: Alexander Diewald's 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: Alexander Diewald's avatarAlexander Diewald <diewald@fortiss.org>
      6c64c932
  13. 04 Oct, 2018 2 commits
  14. 01 Oct, 2018 1 commit
  15. 19 Sep, 2018 1 commit
  16. 17 Sep, 2018 1 commit
  17. 18 Apr, 2018 1 commit
  18. 17 Apr, 2018 1 commit
  19. 09 Apr, 2018 2 commits
  20. 19 Mar, 2018 1 commit
  21. 13 Mar, 2018 1 commit
  22. 09 Feb, 2018 1 commit
  23. 30 Jan, 2018 1 commit
  24. 06 Dec, 2017 1 commit
  25. 04 Dec, 2017 1 commit
  26. 01 Dec, 2017 1 commit
  27. 29 Nov, 2017 1 commit
  28. 28 Nov, 2017 1 commit
  29. 21 Nov, 2017 1 commit