Release 2.0.0

- 9.0.1
- 9.0
- 8.4
- 8.3.1
- New M2M Model checker provided
- The MappingRule option 'Strict matching' has been added
- JSRunnable Stereotype is no longer a New-term
- The profile RhapsodyModelManager removed from target model
- When a Unit is removed from project, the M2M Engine removes physical files as well
- If a Profile is in source profiles of the M2MRuleset, and also in the target profiles, it is not removed at the end of the transformation
- Fix on TraceabilityReport results
- Migration mode is removed from the M2MRuleset. By default, if source equals target, it is considered as migration MappingRule
- Aggregates Multiplicity properties are added in the M2M profile
- Set Target package as scope of the TraceabilityReport Table
- JSFunction and JSRunnable checkers are added
- The context menu "M2M" is renamed "M2M Launcher"
- Delete property M2M_Transformation_DeleteOSLCLinks on M2MRuleset
- A warning message is now logged when a transformed element has its owner not mapped and without New Context function on his MappingRule
- Fix bug when removing Unit files of filtered Packages with Rhapsody 8.3.1 and 8.4
- New property to transfer behavioral diagrams in the target model
- Log M2M version, Rhapsody version and if the JVM is in debug mode