Skip to content
Snippets Groups Projects
  1. Apr 15, 2020
  2. Apr 09, 2020
  3. Mar 30, 2020
  4. Mar 26, 2020
  5. Mar 17, 2020
  6. Mar 15, 2020
  7. Mar 03, 2020
  8. Feb 18, 2020
  9. Feb 03, 2020
  10. Jan 15, 2020
  11. Jan 13, 2020
  12. Dec 20, 2019
  13. Dec 19, 2019
  14. Dec 09, 2019
  15. Nov 14, 2019
  16. Nov 08, 2019
  17. Oct 22, 2019
  18. Oct 18, 2019
  19. Oct 15, 2019
  20. Oct 13, 2019
  21. Oct 10, 2019
  22. Sep 04, 2019
  23. Sep 03, 2019
  24. Sep 02, 2019
  25. 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
Loading