2.12.2021, 9:00 - 11:00: Due to updates GitLab may be unavailable for some minutes between 09:00 and 11:00.

  1. 27 Nov, 2018 1 commit
  2. 26 Nov, 2018 4 commits
  3. 22 Nov, 2018 2 commits
  4. 21 Nov, 2018 9 commits
  5. 16 Nov, 2018 2 commits
  6. 15 Nov, 2018 6 commits
  7. 09 Nov, 2018 1 commit
  8. 11 Oct, 2018 1 commit
  9. 10 Sep, 2018 1 commit
  10. 04 Sep, 2018 1 commit
  11. 03 Sep, 2018 1 commit
  12. 17 Aug, 2018 6 commits
  13. 03 Aug, 2018 1 commit
    • Stefan Schuhbaeck's avatar
      move migration logic back to MigrationAssistant, add MigrationUtil · 8375f258
      Stefan Schuhbaeck authored
      Features (MigrationUtil):
      
      * create new Transformation and Identity files: This will use the
      current identity    Transformation as starting point for the new
      version. The new version string is automatically included in the new
      files. The files will be created based   on the defined naming
      convention and saved in VadereSimulator/resources
      
      * automate scenario migration without gui: The MigrationUtil will
      migrate   all scenario files within the specified directory and all
      child directories.
      
      To exclude specific sub-trees or only specific
      directories the igonoreDirs List can be expanded.
      
        To exclude sub-trees or specific directories without code change add
        one of the following marker-files to the directory.
      
        * DO_NOT_MIGRATE or .DO_NOT_MIGRATE: Ignore current directory but
          continue with existing child directories.
      
        * DO_NOT_MIGRATE_TREE or .DO_NOT_MIGRATE_TREE: Ignore the directories
          and the complete sub-tree.
      
        Use the marker files from the Tools directory. These files have a
        comment to explain for what they are used for.
      
        The content of the file is not used, only the file name is needed.
        These files must be added to the git cache to work.
      
       * automate migration revert: This will use the revert function of the
         MigrationAssistant to revert a migration if the <file-name>.legacy
         files still exist. For this to work the legacy file must be in the
         same directory as the scenario-file
      8375f258
  14. 02 Aug, 2018 2 commits
  15. 01 Aug, 2018 1 commit
  16. 30 Jul, 2018 1 commit