Community
Participate
Working Groups
Two suggested improvements (1) when adding a related instance, an association instance should be programmatically added between the new instance and the one that the action was started from. (2) the action needs to take into account inheritance - I'll add an attachment on this
(3) This action should not include extends (or implements) relationships, which don't make any sense for instances - these need to be removed from the "Add Related Instances' - 'Select Related Artifact' dialog box
Created attachment 181604 [details] enh Feature should operate as per attachment.
This issue is a mixture of bugs and enhancement - feel free to re-classify if you wish
Created attachment 183577 [details] Patch_1
Hi Chris, I fixed what you requested for. Please, check whether all right.
I only use the production profile. If you believe you have completed it, then apply the patch and I'll check it out after the next release (or Navid can check it for you)
Yes, I'll verify the patch (Chris can only check out the changes at the end of an iteration).
I applied patch from Valentin.
Please see attachment for the scenario that's failing.
Created attachment 183939 [details] Class Diagram Consider the attached class diagram. Three entities A, B, C with associations to one another. When A is dragged on an instance diagram and 'Add related artifacts' are added, it correctly identifies B and C. However when they're both selected and inserted, it seems to insert two instances of B with incorrect associations.
Created attachment 183940 [details] Instance diagram See result of instance diagram when an instance of A is added and user selects 'add related instances'. Two instances of B are added and the associations are incorrect.
Created attachment 183995 [details] Patch_2
Hi Navid, I have fixed your issue. It was all a consequence of this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=328853
This patch already applied.
Thanks Valentin! Fix has been verified.
