Create a correct hash for reuse elements and use it for detecting updated reuse elements
Related to #4125 (closed)
Prio: low
In case of reuse, an element is extended with a reuse specification. This specification contains also a hash for this element. This hash should indicate if a reuse element is still the same or if it was (somewhere else) updated (--> same hash as before = no update and vice versa).
Currently, the specification has already a hash attribute, but it is for all elements always "todo". The correct creation of a hash and its usage to detect updated reuse element should be implemented.
Testing:
- Create a new AF3 project with a component architecture (if your projects contain old reuse elements/libraries, you will probably need to delete them since the hash field type within the reuse meta model has changed)
- Create three components (A, B, C)
- Add A, B and C to a new reuse library R1 ("Add to Reuse Library")
- Add C to another new reuse library R2
- Create a second AF3 project with a component architecture where you reuse B and C from R1 and C from R2
- Within this second project, change slightly the reused elements (the one B and the two Cs) and perform for all three a library update ("Update in Reuse Library")
- Go back to the first AF3 project
- Right click on A (in the project tree) and use "Get reuse update information": it should say that no origins were updated
- Right click on B (in the project tree) and use "Get reuse update information": it should say that one origin was updated (in R1)
- Right click on C (in the project tree) and use "Get reuse update information": it should say that two origins were updated (in R1 and R2)
Edited by Sebastian Bergemann