- If the creation of new annotations should be wrapped into a command, but the annotation already exists, avoid the usage of a command and just directly return the (already existing) annotation.
- This avoids superfluous model modifications (i.e., the project marked dirty and requires saving)
refs 2369

- When inserting copies of objects as a result of a copy&paste operation, the inserted model elements is shifted by an offset. This gives visual feedback to the user that the paste operation has actually been performed.
- Notes:
 + Some model types are not handled yet (see ticket)
 + Although maybe an obvious approach, this feature cannot be implemented as a method in HierarchicElementCompositorBase:
   o It is not the base class of all affected compositors
   o HierarchicElementCompositorBase resides in org.fortiss.tooling.base, where as the required methods for detailing with layout information are in org.fortiss.tooling.base.ui
refs 2344

refs 2240

- Add IAnnotationValueProvider.isHidden() that allows to hide annotations from any view (useful for internal attributes that should not be exposed to the user). Default = false
- Extend AnnotationEntry and AnnotationFilter accordingly

- Prevent pollution of AnnotationEntry <-> IModelElement cache via instantiateAnnotations(final IModelElement element) (which might be invoked from model transformations). I.e., the cache is only updated, when the AnnotationEntries are queried from the GUI context.
- In case further measures need to be taken to limit the size of the AnnotationEntry <-> IModelElement cache, <http://stackoverflow.com/questions/2941283/java-fixed-memory-map> might be a good starting point

- Add prefix "generated-" for directories of generated edit and editor code (not used in default AF3 distribution)

- Undo last two changes: will be handled by ElementCompositorService (in the kernel)

refs 2309

refs 2309

- Assign unique IDs to annotations as soon as the are instantiated (before, annotations relied on the ID-fixup that is triggered when the model is persisted)
refs 2309

Fixes a bug in the EStructuralFeatureValueProvider that caused the Enum filter list to be applied on objects that should not be filtered.

Adds the possibility to filter the list of available choices for an enum-type annotation via the annotation's value provider.
Therefore, a map containing the class of the to be filtered model elements and the allowed enum literal must be given in the constructor of the value provider.

DerivedAnnotationValueProviderBase.setAnnotationValue(): Convert String-encoded input to actual data type

refs 2240

generalize RequirementSpecificationUtils.removeRequirementSpecifications() to 
BaseModelElementUtils.removeModelElementReferenceSpecifications()
  
refs 2240

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

- Add Id, version, and ConQAT tags to XML files

* Mainly documentation cleanup
* Remove some commented out code

org.fortiss.tooling.kernel.internal.storage.eclipse.ModelContext:
org.fortiss.tooling.kernel.utils.EMFResourceUtils:
 - Resolve B.19 issue (numbering scheme as of Aug. 14, <https://af3-developer.fortiss.org/projects/autofocus3/wiki/Check-list_for_Code_Reviews/56>) "Use static imports"
refs 2255

refs 2208

- Fix addition of spurious undo/redo command by ensuring that annotations are instantiated from HierarchicElementCompositorBase.compose()
- Derived compositors that override compose() must ensure that call their parent classes' implementation
refs 2208

- Move annotation value service, annotation value provider base classes and annotation extension point to org.foritss.tooling.base
- Remove createEditingSupport() from IAnnotationValueProviderBase and move functionality to org.fortiss.tooling.base.ui.annotation.editingsupport.EditingSupportFactory instead
- Rename extension point to org.fortiss.tooling.base.annotation.

Example binding:

<extension point="org.fortiss.tooling.base.annotation">
  <annotation binding="org.fortiss.af3.timing.annotation.valueprovider.CIValueProvider">
     <modelElementClass modelElementClass="org.fortiss.af3.component.model.Component"/>
  </annotation>
</extension
- Adapt all known users of annotation framework to new structure
- The change is a preparation to fix #2208, i.e. to put the instantiation of a model element and its annotations into a single undo/redo command
refs 2208

- Document that getAnnotation(IModelElement modelElement, Class<T> clazz) wraps the model access into a command
refs 2199,1841

- Ensure that that AnnotationsUtils.getAnnotation(IModelElement modelElement, Class<T> clazz)  actually wraps the extraction / creation of an annotation into a command
- DAGExtractionWithoutDeployment: use this variant
refs 2199,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

  - 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