UML24 — Associations with same name that live in different packages violate unique name constraint

Some associations that have the same name, but exist in different packages in the unmerged model, show up together in the merged model violating the unique name constraint

BasicActivities::A_outgoing_source (Figure 12.5) and BehaviorStateMachines::A_outgoing_source (Figure 15.2).
BasicActivities::A_incoming_target (Figure 12.5) and BehaviorStateMachines::A_incoming_target(Figure 15.2).
BasicComponents::A_realization_abstraction (Figure 8.2) and AuxilliaryConstructs::InformationFlow::A_realization_abstraction (Figure 17.2)

One way to fix that is to rename the associations to avoid the name collission, for example:

BasicActivities::A_outgoing_source_node and BehaviorStateMachines::A_outgoing_source_vertex
BasicActivities::A_incoming_target_node and BehaviorStateMachines::A_incoming_target_vertex
BasicComponents::A_realization_abstraction_component (Figure 8.2) and AuxilliaryConstructs::InformationFlow::A_realization_abstraction_flow (Figure 17.2)

• • This fix affects the respective figures to show the non-default association names explicitly

Agree to the suggestion given in the issue.