Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Sirius/Modularization"
< Sirius
(→Git Repository Layout) |
(→Git Repository Layout) |
||
| Line 4: | Line 4: | ||
The source code will be in a single Git repository, organized in the following directories: | The source code will be in a single Git repository, organized in the following directories: | ||
| − | * <code>plugins</code>: source code for all the plug-ins | + | * <code>plugins</code>: source code for all the plug-ins of Sirius itself; |
| − | * <code>features</code>: feature definitions; | + | * <code>doc</code>: the documentation plug-ins; |
| − | * <code>releng</code>: parent project (for the root POM and shared files), target platform definitions, update- | + | * <code>examples</code>: example Sirius modelers and sample metamodel definitions used by the examples and/or the tests; |
| + | * <code>tests</code>: automated tests (JUnit and SWTbot); | ||
| + | * <code>features</code>: feature definitions (including doc, examples and test features); | ||
| + | * <code>releng</code>: parent project (for the root POM and shared files), target platform definitions, update-sites definitions; | ||
* <code>tools</code>: 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. | * <code>tools</code>: 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. | ||
Revision as of 09:36, 29 July 2013
As part of the move to Eclipse, which implies a complete renaming (and thus API break) for the existing Viewpoint code base, 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.
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.