Community
Participate
Working Groups
Other tools collect all the associations together in a folder in the "Model Explorer/Project Explorer". This aids the user when they wish to sort the classes in the project in that the classes are not interspersed with associations. This is a very common use-case for large model management. This improvement to the the Simple UML Facet would be appreciated by most if not all users.
New Gerrit change created: https://git.eclipse.org/r/97472
New Gerrit change created: https://git.eclipse.org/r/111065
> New Gerrit change created: https://git.eclipse.org/r/111065 This is a first version of the contribution. I just realized that the "Link with Editor" in the ModelExplorer doesn't play well with Facets. Although the ContentProvider provides its own algorithm to reveal semantic elements (Taking customized references into account), it is wrapped in the CommonViewer / Common Navigation Framework, thus is not directly accessible. So the reveal algorithm is very generic and simply browses the containment tree up. As a result, it is only able to expand the tree up to the association's parent (The association itself is hidden behind a custom 'associations' reference). As far as I can tell, there is not much we can do about this issue There may potentially be other issues related to this patch: I'm not sure how many UML Elements may own references. I've identified Package#packagedElements, Class#nestedClassifiers and Interface#nestedClassifiers. If there are other options, associations will appear twice: once under the parent directly, and ane more time behind the "associations" custom reference.
The issue I mentioned above is tracked in Bug 484648
