- Install EAdapter for top level element of current project (instead of switching it the currently active root element (e.g., component architecture)).
- This ensures that annotation views are updated also on changes of models that currently do not have the focus (i.e. programmatic changes of models that are currently not shown in the diagram view)
refs 1841

- Display model element ID in tooltip (in addition to model element name). This is useful to identify selection targets for annotations of type EReference where the editor also displays the ID in order to distinguish elements with the same name.
refs 1841

- Add isAvailableObject() method that can be overridden by value providers in order to filter the set of available elements

LabelValueMapping: Use this filter
refs 1841

refs 1841

- TextEditingSupport / ElementEditingSupportBase: Unset value if users enters the empty string
refs 1841

Modify the DerivedAnnotationValueProvider (org.fortiss.tooling.base.ui), such that the editability of the annotation editing support mirrors the behavior of the derived annotation.

- Remove support for multiple selections of values since it is not supported by EMF which enforces that the lists used to implement features with multiplicity > 1 are unique:

<https://www.eclipse.org/forums/index.php?t=msg&th=133621&goto=417016&#msg_417016>

refs 1841

refs 1841

refs 1841

- Support to select an element more than once (enabled by default). In order to disable this feature, use the map-based constructor of EStructuralFeatureValueProviderBase and construct the EStructuralFeature accordingly.
- Fix update of Ok button when deselecting all elements (fire second event to work around bug in DualList base class)
refs 1841

refs 1841

refs 1841

refs 1841

- Do not cache LabelValueMapping since {@link IDerivedAnnotation}s support that the {@link {EStructuralFeature} of their return value is changed at runtime
refs 1841

refs 1841

refs 1841

refs 1841

- Do not expose createComboBoxLabelValueMapping()
- Instead, provide getLabel()
refs 1841

- Implement MultiSelectionEditing support that currently supports the selection of multiple values for EReferences (based on OPAL's DualList)
- Rename ComboBoxLabelValue mapping -> LabelValueMapping
- Update AnnotationViewPartBase also on ADD_MANY / REMOVE_MANY events
refs 1841

- Add private getAnnotationValueProvider() method
refs 1841

  - Remove getEStructuralFeatureOf()
  - Expose DEFAULT_KEY (from AnnotationValueProviderBase)
  - createEditingSupport(): Pass current specification

- AnnotationEntry:
  - Remove getSpecificationElementFeature()
  - Add getSpecification(). TODO: Use this method internally in AnnotationEntry
  
- EStructuralFeatureDescriptor
  - getEStructuralFeature(): Pass current specification
  
- Base on the above, no longer base logic to compute the currently active EStructuralFeature for IDerivedAnnotiations on a temporary EStructuralFeatureDescriptor
refs 1841

- Adjust all annotations that inherited from IDerivedAnnotation to use the new DerivedAnnotationBase class
- EOperation cleanup
- Move getValue() from org.fortiss.tooling.base.utils.AnnotationUtils to org.fortiss.tooling.base.model.base.impl.DerivedAnnotationBaseStaticImpl

refs 2171

- This should fix the related crashes that contained multiple objects with the same name
refs 1841

- Add AnnotationInstantiationMigrationProvider that augments loaded models with annotations that have been added to the AF3 installation after the creation of the model.
- Note that:
  - It is still required to use AnnotationUtils.getAnnotation() to obtain (and potentially instantiate) an annotation. This is because annotations are only instantiated for newly added model elements if the annotation view is visible.
  - IMigrationProviders that convert old attribute values into annotations cannot rely on the fact that the annotation instance already exists (since the execution order of the IMigrationProviders is not defined). Hence, the need to use AnnotationUtils.getAnnotation(modelElement, clazz, false) to obtain (and potentially instantiate) an annotation (without wrapping the model access into a command, see #2010).
refs 1841

- Prevent nested calls of selectionChanged() which could trigger a refresh of the table before all column label providers / editing support has been initialized
refs 1841

  - Add getAnnotation(IModelElement, Class<T> clazz, boolean)  variant that lets the caller control if the potential instantiation of an annotation should be wrapped into a command.
  - The original getAnnotation(IModelElement, Class<T> clazz) variant still exists and still defaults to wrapping the instantiation into a command
- AnalysisMigrationProvider / SafetySpecToAnnotationMigrationProvider: Use the new method to prevent the creation of a command in order to prevent the use of the IPersistencyService during the migration (workaround for the annotation-related aspect of #2010)
refs 2010,2172

 - List<AnnotationEntry> getValues(IModelElement element) --> AnnotationEntry getAnnotationEntry(IModelElement element);
 - The semantics of the method is change to return exactly the AnnotationEntry that contains the AnnotationValueProvider-to-IAnnotatedSpecification mapping for the given model element. In the old semantics, a list of all annotation entries for model elements that had the same type as the given model element have been returned.

AnnotationEntry:
 - add isEmpty()

Consequences:
 - Fix update bug of GenericAnnotationView when deleting model elements (stale rows used to stay in the view)
 - Performance improvement

TODO: The GenericAnnotationView is still very slow during the deletion of large sub-models (and probably also during addition e.g., because of c'n'p of large sub-models) 
refs 1841

  - Moving dependencies to org.fortiss.tooling.common.ui
  - Setting minimum required version to 3.7.1

- Remove redundant dependencies (i.e., those, that are already contained and re-exported by the actual dependencies)

- getAnnotation(): Wrap creation of new Annotation into command since this method might easily be called from a context that cannot directly manipulate the model (e.g., from the GUI context)
refs 2178

SafetyUtils.getParentSpecificationsWithType() --> AnnotationUtils.getParentAnnotationsWithType()

AnnotationUtils: Add TODO to remove workaround that should be no longer required after IDE dev tools update.
refs 2171

Add <T extends IAnnotatedSpecification> T getAnnotation(IModelElement modelElement, Class<T> clazz),

a method to safely obtain an annotation for a given modelElement (and to create it, if it does not exist yet).
refs 1841

a method to determines the {@link EClass} corresponding to a give {@code clazz} (typically the interface for the generated implementation class of an Ecore meta-model).

- Show model element name in tool tip (useful,  if name is not visible due to scrolling to the right)
refs 1841

  - Crash when setting an annotation type based filter
  - Missing updates for filters that depend on the currently selected model element
refs 1841

  - Move label provider to dedicated package
  - Move generic annotation view to dedicated package
  - Move inner classes of GenericAnnotationView to separate classes (filter support in dedicated package)
- Small documentation updates
- No functional change
refs 1841