- add setAnnotationValue(String value, T specification) in addition to setAnnotationValue(V value, T specification) variant
 - This enables to use the String-based AnnotationEditingSupportStandard for non-String annotations.
 - Concrete AnnotationValueProviders must implement this method and convert the String representation of the input to the storage format provided by the respective annotation class (e.g., for Double, just by using the Double(String) constructor)
 - The current implementation  has been tested with String, Double, enum and multiple value String annotations

- TODO:
  - Cleanup of IAnnotationValueProvider
  - Base class hierarchy for common concrete annotation value providers
  - multiple value annotation support in GenericAnnotationView

refs 2049

refs 2061

refs 968

refs 2048

Modified 'GenericAnnotationView' to have a simpler dispose logic for the table's columns. Additionally, this provides a more convenient logic for subclasses.

- Refactored the annotation code to avoid duplicates and provide classes for easier re-use in other projects
- Added several comments
- Added a boolean flag to the value provider interface for simple implementation of annotations storing multiple values

- Modified 'GenericAnnotationView' to load custom Editing elements in the table if provided

refs 2035

refs 1841

refs 1841

refs 2021

refs 2021

refs 1960

refs 135

small fix -> schedule generation of manual deployments (yet not working correctly for shared memory architectures)

refs 1841

refs 1841

refs 1841

refs 1841

refs 1841

refs 1841

Fixed the issue. Made the behavior general: any model whose behavior on double click is undefined will trigger the display of the properties tab. Can only be better than nothing it seems. If not, it will be easy to revert.
refs 1911

refs 1882

refs 1612

refs 1612

refs 1855

refs 1841

refs 1841

refs 1841

refs 1778

refs 1758

refs 1601

refs 1612

refs 1739