Update CHANGELOG.md for CodeRT 2.0.7 release

Author: chaitanyavalli-r

docs-sources/releases/CHANGELOG.md

@@ -1,3 +1,17 @@
+# 2.0.7 (2025-05-06 11:34)
+1. Java 21 is now required for running the Art language server. Using Java 21 instead of Java 17 gives some performance improvements and enables use of more modern Java.
+2. In diagrams that use manual layout it's now possible to move some of the text labels. For example, it's possible to move the name label of a transition which can make a state diagram more readable by avoiding that the label overlaps with other contents of the diagram.
+3. Layout files for manual layout are now created, updated and deleted when diagrams are saved, instead of immediately when the manual layout setting is modified. This makes the manual layout setting work consistently with other diagram settings.
+4. Layout files for manual layout are now updated when referenced Art elements are renamed. This ensures that layout information in most cases stays valid when an Art file is changed. If an element with diagrams, such as a capsule, is renamed, the diagram is automatically reopened to reflect the new name.
+5. Automatic updates of references to Art elements in layout and diagram setting files now also happen when the elements are renamed by means of the Rename command (i.e. when performing a "refactor rename"). Undo/Redo now also works for this scenario.
+6. If a diagram is "dirty" (i.e. has unsaved changes in diagram and/or layout settings), and an element shown in the diagram is renamed, then references to the element in the diagram and layout settings will now be merged with the unsaved changes, so that all changes will be persisted when you save the diagram. For the special case when the element that "owns" the diagram is renamed, you will be prompted to save the changes as part of automatically reopening the diagram.
+7. The form-based TC editor (which you open by the **Edit Properties (UI)** command) now shows in its header if the TC has any custom properties defined. If there is at least one custom property a link **More Properties** appears. If you click this link, a "quick pick" popup will appear and let you navigate to the custom properties in the TC text editor. In addition to custom properties this feature is also useful for navigating to properties which the form-based TC editor doesn't (yet) support, such as `threads`.
+8. The form-based TC editor now groups TC properties into three separate tabs **General**, **Code Generation** and **Build**. This makes it easier to find and edit a certain property and avoids excessive vertical scrolling through all properties.
+9. It's now possible to visualize the inheritance of C++ types in class diagrams. The types must be defined in `[[rt::decl]]` code snippets in one or many Art files. Right-click in the `[[rt::decl]]` code snippet and select the class (or struct) that you want to generate a class diagram for. All base classes for the selected class will be shown in the diagram. Read more about this feature in [the documentation]({$vars.doc.server$}/working-with-art/diagrams/#class-diagrams-for-c-code).
+10. Log streams have been extended so they now can write log messages to text files. A new TargetRTS class `RTLog::Stream` provides a uniform interface for writing log messages to any `std::ostream`.
+11. The C++ code generator now supports generation of type descriptors for C++ types that are defined in C++ source files and there marked with the `[[rt::auto_descriptor]]` or `[[rt::manual_descriptor]]` attributes. This means that it's no longer necessary to place such types in Art files (inside `[[rt::decl]]` code snippets). This simplifies the use of already existing C++ types in a realtime application when type descriptors for those types are required. Read more about this feature in [the documentation]({$vars.doc.server$}/art-lang/cpp-extensions/#type-descriptor).
+12. Version 2.0.0 of the Art Exporter is now available. It has been redesigned and is now provided as part of the Model Compiler. This makes it possible to run it from the command-line, and also ensures that generated C++ code is identical to what was produced with Model RealTime. The new Art Exporter implements initial support for transformation configurations, capsules, ports and protocols, which means that complete executable applications now can be migrated from Model RealTime to Code RealTime. See [this page](https://model-realtime.hcldoc.com/help/topic/com.ibm.xtools.rsarte.webdoc/Utilities/Art%20Exporter.html) for the full list of improvements.
+
 # 2.0.6 (2025-03-18 09:38)
 1. Manual layout of diagrams is now supported. This means you can move symbols around to manually decide their positions on a diagram. This is currently an EXPERIMENTAL feature. To try it out, mark the checkbox "Manual" under "Layout" in the properties view of any diagram. Read more about this feature [here]({$vars.doc.server$}/working-with-art/diagrams/#automatic-vs-manual-layout).
 2. It's now possible to use log streams for logging messages from your application. They have a number of benefits compared to using log ports. For example, you can use them from anywhere (not just from a capsule), standard C++ stream manipulators can be used (for formatting etc) and you can use them either for logging to `stdout` or `stderr`. Compound log messages can be printed in a thread-safe way by locking the log streams to avoid interleaved log messages from other threads. Read more about this feature [here]({$vars.doc.server$}/target-rts/logging/#log-stream).