Sirius/Modularization

The move to Eclipse, which implies a complete renaming of the existing Viewpoint code base, implies by definition a major API break. We want to take this opportunity to improve the code modularization. This page describes the target organisation and the actions needed on the current code base to get there.

Note: The page may sometimes refer to the structure of the source code before the conversion to Eclipse, which is not publicly visible.

Git Repository Layout

The source code will be in a single Git repository, organized in the following directories:

• plugins: source code for all the plug-ins of Sirius itself;
• doc: the documentation plug-ins;
• examples: example Sirius modelers and sample metamodel definitions used by the examples and/or the tests;
• tests: automated tests (JUnit and SWTbot);
• features: feature definitions (including doc, examples and test features);
• releng: parent project (for the root POM and shared files), target platform definitions, update-sites definitions;
• tools: source code for development tools that contributors must install in their development environment (e.g. Acceleo generators used to generate parts of the source code). These are not part of Sirius but are required to develop Sirius.