You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When propagating Java packages to UML, different packages with the same suffix (e.g., aroguml.org.util and argo.util) are considered as the same package and thus incorrectly merged during propagation. Consequently, elements being contained in the Java package that is propagated second are placed in the Java package that was propagated first.
A possible solution would be to adapt the Java2UML-Reactions in order to match packages based on their full namspace (i.e., fully qualified name).
The text was updated successfully, but these errors were encountered:
When propagating Java packages to UML, different packages with the same suffix (e.g., aroguml.org.util and argo.util) are considered as the same package and thus incorrectly merged during propagation. Consequently, elements being contained in the Java package that is propagated second are placed in the Java package that was propagated first.
A possible solution would be to adapt the Java2UML-Reactions in order to match packages based on their full namspace (i.e., fully qualified name).
The text was updated successfully, but these errors were encountered: