| commit | 8f07ef824fd3bf25e8b2b56d334f9fdec263fe4e | [log] [tgz] |
|---|---|---|
| author | Laurent Redor <laurent.redor@obeo.fr> | Fri Feb 19 09:09:14 2021 +0100 |
| committer | Laurent Redor <laurent.redor@obeo.fr> | Fri Feb 19 14:36:00 2021 +0100 |
| tree | 84f48c065bd9d6009a87b0849b2cee283200b01d | |
| parent | 42a59bf47371f644d87f9306e83c2eef48bca957 [diff] |
[571361] Add corresponding tests A label has been manually added in the diagram "Basic Executions Diagram" and "Basic Executions Diagram Raw" to reveal the problem of label on border in sequence diagram. In theory, in the Interaction VSM sample, the execution label is on border but with a "blank" label. So it has been possible to add manually a label directly in the VSM. This modification allows to see visually the difference, for example by setting the MappingBasedSiriusFormatDataManagerExistingTargetSequenceDiagramTest.MB_SEQ_GENERATE_IMAGES_TEST_DATA to true. And then to compare mb_seq_ed_from___storedFormat-Basic__Executions__Diagram___to___storedFormat-Basic__Executions__Diagram__Raw__full_from.png to mb_seq_ed_from___storedFormat-Basic__Executions__Diagram___to___storedFormat-Basic__Executions__Diagram__Raw__full_to.png. But even without this modification the sequence tests are KO because there are "invisible" border label for all executions. These labels are not visible but they have coordinates (changed by the fix). Bug: 571361 Cherry-picked-from: 571304 Change-Id: Idc58d66536af1e8c340de02ac199125baad60ba3 Signed-off-by: Laurent Redor <laurent.redor@obeo.fr>
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.
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.