Skip to main content
Jump to: navigation, search


< Sirius
Revision as of 10:48, 24 October 2014 by (Talk | contribs) (New & Noteworthy)

THIS IS A DRAFT. Sirius 2.0.0 is not released yet.

Sirius 2.0.0 is a major release which focuses on better usability of diagrams, performance improvements, and better modularity. It also includes extensive automated test suites.

See also [TBD the announce on the mailing list].


Sirius 2.0.0 was released on 2014-10-24 (tag v2.0.0, commit 8d6bc1807872a40e3e2a6e37e280067e07265072). It is available from the following update sites:

It is recommended you use the update-site matching the version of Eclipse you use to avoid potential issues at runtime.

This version includes the complete JUnit and SWTBot test suites used to validate Sirius. They are published along with all their dependencies in separate update-sites from the core, available at:

If you want to install the feature, which provides APIs to help create automated tests of Sirius-based modelers, you will need to add the following update-site:

If you want to install and run the test suites themselves, you will also need the following additional update-site:

It is needed to run the tests which use an old query language (which is now superseded by Acceleo 3 and the core feature:/var:/service: interpreters).

Juno users: Sirius depends on more recent versions of some components that what is available by default from a Juno install. You need to add the following update-sites if you want to install Sirius 1.0.0M7 on Juno:


Sirius 2.0.0 is compatible with the following versions of Eclipse:

  • Eclipse 3.8/4.2 (Juno)
  • Eclipse 4.3 (Kepler)
  • Eclipse 4.4 (Luna)

It should also be compatible with milestone builds for Eclipse 4.5 (Mars), although this has not been thoroughly tested.

New & Noteworthy

The complete list of (109) tickets fixed in Sirius 2.0.0 can be found here on the Bugzilla.

The major themes for this version were:

  • Ergonomic Improvements on Diagrams: see below.
  • Better Performance and Scalability: see this blog post for additional information and the list of corresponding tickets for the raw details.
  • Contribution of the Automated Test Suites (JUnit and SWTbot) with more than 4500 automated tests.

Ergonomic Improvements on Diagrams

  • #443381: When diagram elements are selected, simply hitting the "Escape" key will deselect everything. Before this, it was necessary to click on the diagram's background to disable the selection, but the background is not always visible.
  • #443108: A new action is available on diagram edges to "straighten" them, removing all the intermediate bend-points which may have been created by previous manipulations.
  • #442289: A new family of actions is available when several elements are selected on a diagram, to distribute them (horizontally or vertically) with uniform spaces between them.
  • #441424: When resizing a node of container, the anchor of the incident edges are kept at the same visual location. Before that, the could move proportionally to the resize.
  • #438691: It is now possible to select element that intersects the selection rectangle and not that is completely contained by the selection rectangle. This new behavior is enabled when user selects elements from right to left. The normal mode (previous mode) remains when the user selects elements from left to right.
  • #437095: The edges appearance is now kept, as much as possible, when one of its extremity is moved. A move of an extremity should move only the closest segment of the edge.
  • #437097: The edges appearance is kept as much as possible when a node (container or not) is moved. A move of a node now impacts only the closest segment of the linked edges.
  • #441090: When a node, container or not, is resized to the left, upwards, or both, the location of its children (elements inside a container and border nodes) is not changed. It is possible to retrieve the previous behavior by pressing the F3 function key during the resize.

Performance Improvements

Other Significant Changes

Known Issues

The following important issues are present in the 2.0.0 release. They were identified after the code freeze and could not be fixed in time. If possible (i.e. no API break needed), they will be fixed in 2.0.x maintenance releases.


Back to the top