Impossible to map operations define in parent features

[Céline Bensoussan]

In the Association concern, when in a leaf feature, I try to map operations from Data defined in parent features but not all operations show. See screenshot of feature ArrayList, the operations from the feature Association (size and contains) are not showing. However, if I go to Kind or Ordered, I can map those operations.

[Matthias Schoettle]

Similar to #321, except that it happens when a structural feature (e.g., an association end) from an extend aspect is called directly. Then, the RAMModelUtil.collectClassifiersFor(...) method cannot find the real classifiers because it cannot handle mapped classifiers properly (into both directions).

[Matthias Schoettle]

References #372: Changes the way classifiers (based on extends with name and mappings (in extends and reuses)) are collected. The classifiers are collected recursively to consider all cases in the complete hierarchy.

In case a classifier is passed that is not contained in the current aspect, the corresponding classifier of the current aspect is first determined and the "bottom-up" approach to collect all classifiers is performed (as described above).

→ <<cset 4cec1a0daaa7>>

[Matthias Schoettle]

Merged in Issues/372-FixCollectClassifiers (pull request #59)

[Matthias Schoettle]

References #372: Fixes a problem that occurs when the to element of the classifier mapping is not set yet (but the from element is). For example, in Association and KeyIndexed, such a mapping from Key is created.

→ <<cset 3d14904f71c5>>