refs 3194

refs 3194

TODO: Ratings of documentation HTML files (depends on #3195)
refs 3177

refs 3177

refs 2591

refs 3192

Please fix your SVN configurations!

See https://af3-developer.fortiss.org/projects/autofocus3/wiki/Developer_Installation, Section "Initial Workspace Content Check-out", §6.

refs 2490

Class is used by exploration.alg plugin (to be included into next release).

Since its methods are generally applicable to migrate models based on concepts introduced in tooling.base, this MigrationUtils should remain (as a counterpart to tooling.kernel's MigrationUtils).
refs 2490

Remove further unused methods in BaseModelElementUtils
 - nonHiddenSpecifications()
 - getConnectedElements()
refs 2490

(Removed erroneous and unused method BaseModelElementUtils.getSuccessorConnector())
refs 2490

refs 2490

refs 2490

refs 2490

refs 2490

refs 2983

- Add parser interface for exploration expression language (visitor). This includes an additional EOperation for IExpressions to accept visitors.
- Implement a base class for expression evaluators.
- Add a Deployment validator that performs an evaluation against a given ExplorationSpecification and which uses expression evaluator base class.
- Add a context menu entry to launch the Deployment validation.
- Add two Utility methods to handle integer and floating point numbers.
refs 2960

refs 2885

refs 2779

- Check each pasted referenced element if it can be pasted to the target annotation.
refs 2361

Add a utility method to get the directly connected elements of a given IHierarchicElement that have the given type.

- Add a migration util method for IAnnotatedSpecifications.
- Documentation cleanup.
- Minor refactoring.

- Copy operation are not dirtying the model any more: Add a write flag to annotation actions; Only those will are dirtying a model now.
- Context menu in the annotation view is no longer visible for non-editable annotations.
- References and multi-references are now correctly handled:
  - Correct the set logic.
  - Offer two kinds of pastes for multi-reference annotations: append, replace.
- Fix duplicated context menu entries for the SafetyIntegrityLevel annotation (details: see bug report).
refs 2361

- Move the getEStructuralFeatureDescriptor method to the IAnnotationValueProvider interface.
- Move the getContectMenuEntries method for AnnotationValueProviders to the ValueProviderBase class.
  - Remove the DefaultAnnotationContextActions interface that provided a default implementation.
  - Add copy & paste Actions to the ValueProviderBase class.
- Improve the handling of (Annotation) instanceKeys in the GenericAnnotationView.
- Generalize the Action to create random values for the annotations of the visible element set in the annotation view:
  - Can handle only Number types up to now.
  - Add a static method in AnnotationUtils that allows to provide this capability in AnnotationValueProviders.
- Add a BaseMathUtils utility class in org.fortiss.tooling.base to handle "dynamic" Number conversions that are not considered in Apache common's MathUtils: Used, e.g., for the randowm number generation.
- Update the EnergyConsumption- & WcetValueProviders.
refs 2361

refs 2653

- This will be performed by the IElementCompositorService that is called from createNewSourceDropContext().
- Doing it here already, will trigger an expensive check for duplicate IDs when the ID assignment is issued for the second time from the IElementCompositorService
refs 2759

- I.e., do this for each specification instead of the "contained" model element. Since
"contained" might already have an any, this would trigger an expensive algorithm to
check if there are duplicated IDs.
refs 2759

- prepareAnnotationEntry(): Comment out warning in case the annotation has not been instantiated yet. In the current situation, it has a performance impact on model transformations.
refs 2228

- prepareAnnotationEntry(): Emit a warning in case the annotation has not been instantiated yet. The goal is to remove the code that instantiates the annotation on the fly in the long run.
refs 2228

Ensure that IDs have been assigned to all new model elements before they are hooked to the project / resource
- Rationale
  - Model elements for which no ID has been assigned, have id 0 (which is the default value). 
  - When the new element is hooked to the resource, ResourceUtils.KernelResourceFactory.KernelXMIResource.getId() is called, which internally calls setId() to synchronize the XMI ID with the AF3 ID. In case the ID is still 0, this implicit call will corrupt the ID -> model object map (by override the mapping for key 0).
- Changes
  - ElementCompositorService: Assign IDs *before* hooking new element to the container (but of course using the container to determine the next free ID)
  - ModelElementCompositorBase: Assign IDs to newly instantiated annotations

refs 2726

refs 2361