[563117] Base implementation of mapping-based format manager

- Use of a <EObject,EObject> (source diagram to target diagram semantic
element) map to resolve FormatData to apply on target diagram based on
source diagram ones.
  - The switch is on the createKey method that resolves using the map
when the semanticDecorator is contained in the source diagram.
- Functional test for the FormatManager.

- Harmonized AdvancedSiriusFormatDataManager interface.

Bug: 563117
Change-Id: I87c073cbbe8b38014a9bd6534191e4ecea8a7726
Signed-off-by: Arnaud Dieumegard <arnaud.dieumegard@obeo.fr>
5 files changed
tree: 5de514a59b6c06ebf8fd5bc24dc61b2f3b4bf4aa
  1. packaging/
  2. plugins/
  3. releng/
  4. .gitattributes
  5. .gitignore
  6. .travis.yml
  7. build.sh
  8. CONTRIBUTING
  9. Jenkinsfile
  10. LICENSE
  11. NOTICE
  12. pom.xml
  13. README.md
README.md

Eclipse Sirius

Build Status

Sirius enables the specification of a modeling workbench in terms of graphical, table or tree editors with validation rules and actions using declarative descriptions.

For more details see the project page and the main wiki page.

Building

The build uses Tycho. To launch a complete build, issue

mvn clean package

from the top-level directory. The resulting update-site (p2 repository) can be found in packaging/org.eclipse.sirius.update/target/repository.

By default the build uses a Neon-based target platform. You can specify a different platform like this:

mvn clean package -Dplatform-version-name=name

where name can be any of the following values:

  • mars (Eclipse 4.5)
  • neon (Eclipse 4.6, the default and reference target platform)
  • canary (uses nightly builds of all our dependencies, only used for testing)

The corresponding target platform definitions can be found in releng/org.eclipse.sirius.targets.