|
|
## Main branches
|
|
|
|
|
|
- `master`: it contains the source code of the latest official release.
|
|
|
- `devel`: it contains the latest source code of the developer version.
|
|
|
- `neon_devel`: it contains the source code of the developer version using old dependences (e.g. Java 8, Eclipse Neon, XText 2.1). This branch is not used anymore.
|
|
|
|
|
|
## Requirements
|
|
|
|
|
|
For the `master` (CHESS version 1.1.0)
|
|
|
|
|
|
- JDK8 for developers, JRE8 for users. Free license JRE8/JDK8: https://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html
|
|
|
|
|
|
For the `devel branch` (CHESS development version)
|
|
|
|
|
|
- JDK11 for developers, JRE11 for users. Free license JRE11/JDK11: https://www.oracle.com/java/technologies/downloads/#java11
|
|
|
|
|
|
## CHESS artifacts
|
|
|
|
|
|
Chess bundles and update sites: https://download.eclipse.org/chess/core/releases/
|
|
|
|
|
|
## CHESS Plugin Creation
|
|
|
|
|
|
The correct procedure to write a compliant plugin should include these steps:
|
|
|
|
|
|
- create a new plugin using the Eclipse wizard **Plug-in Project**. The plugin should be located in the correct repository;
|
|
|
- add the Maven support, right clicking on the plugin name and selecting **Configure/Convert to Maven Project**. Accept the proposed fields, they will be modified in the next step;
|
|
|
- look for the generated file `pom.xml`: edit it by looking at other plugins, in order to share the same hierarchy and configuration;
|
|
|
- if the plugin is not related to a particular group of tasks, locate the file `org.polarsys.chess.parent\bundles\pom.xml` or a more specific parent `pom.xml`. Add the new plugin as `module`. This will include the plugin in the Maven reactor and it will be compiled with others;
|
|
|
- if the plugin should be part of the product, it has to be included in a feature. There are different features that group the plugins by type. Features can be found in the folder `org.polarsys.chess.parent\features`. Select the correct feature and add the plugin in the **Included Plug-ins** section;
|
|
|
- if the plugin is not related to a particular group of tasks, locate the file `org.polarsys.chess.parent\\bundles\\pom.xml` or a more specific parent `pom.xml`. Add the new plugin as `module`. This will include the plugin in the Maven reactor and it will be compiled with others;
|
|
|
- if the plugin should be part of the product, it has to be included in a feature. There are different features that group the plugins by type. Features can be found in the folder `org.polarsys.chess.parent\\features`. Select the correct feature and add the plugin in the **Included Plug-ins** section;
|
|
|
|
|
|
**Note:** tests and JUnit tests should not be included in plugins that will be distributed. They should be located in dedicate plugins that will not be added into the features.
|
|
|
|
|
|
## Generate\Regenerate CHESS profile
|
|
|
## Generate\\Regenerate CHESS profile
|
|
|
|
|
|
See the [Papyrus Guide](uploads/d20a520fcff8b5e1d4045fc5d0a3e5eb/Papyrus_creare_profilo_statico.pdf).
|
|
|
|
|
|
Use the pathed org.eclipse.uml2.uml:
|
|
|
|
|
|
- Neon version: [org.eclipse.uml2.uml_patched.zip](uploads/7fad011964c4e2dac0061852c2581cf9/org.eclipse.uml2.uml_patched.zip)
|
|
|
|
|
|
For additional information read the following posts:
|
|
|
|
|
|
- https://www.eclipse.org/forums/index.php?t=msg&th=207078&goto=662979&#msg_662979
|
|
|
- https://www.eclipse.org/forums/index.php?t=msg&th=1089362&goto=1774168&#msg_1774168.
|
|
|
|
|
|
## [Contributing to Eclipse CHESS](https://gitlab.eclipse.org/eclipse/chess/chess/-/blob/master/CONTRIBUTING.md)
|
|
|
### [Contribution of a non-committer user](https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/97)
|
|
|
|
|
|
### [Contribution of a non-committer user](https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/97 "Contribution of a non-committer user")
|
|
|
|
|
|
## CHESS CI
|
|
|
|
|
|
The following CHESS jobs are available at https://ci.eclipse.org/chess/:
|
|
|
- [devel AUTO build-bundle-release](https://ci.eclipse.org/chess/job/devel%20AUTO%20build-bundle-release/): There is a poll every 10 minutes for SCM changes that triggers the following activities for the 'devel' branch:
|
|
|
1. Run tests
|
|
|
2. Build the code
|
|
|
3. Generate the bundle and the update-site.
|
|
|
4. The artifacts are copied to the public repository https://download.eclipse.org/chess/core/releases/devel/.
|
|
|
- [master MAN build-bundle-release](https://ci.eclipse.org/chess/job/master%20MAN%20build-bundle-release/): This job performs the following activities for the 'master':
|
|
|
1. Run tests
|
|
|
2. Build the code
|
|
|
3. Generate the bundle and the update-site.
|
|
|
4. The artifacts are copied to the public repository https://download.eclipse.org/chess/core/releases/. Remember to change the version of the new bundle:
|
|
|
- in the org.polarsys.chess.configuration.pom.xml
|
|
|
- in the Post Steps script of this configuration.
|
|
|
- [merge-branch-x-to-devel](https://ci.eclipse.org/chess/job/merge-branch-x-to-devel/): Activities to be triggered by the user for the branch to be merged into the devel:
|
|
|
1. In the job configuration (click on 'Configure', section 'Source Code Management/branches to build'), edit the name of the branch that must be merged into 'devel'.
|
|
|
2. Run the job (click on 'Build Now')
|
|
|
- [merge-branch-devel-to-master](https://ci.eclipse.org/chess/job/merge-branch-devel-to-master/): Activities to be triggered by the user for the branch devel to be merged into the master |
|
|
|
|
|
- [devel AUTO build-bundle-release](https://ci.eclipse.org/chess/job/devel%20AUTO%20build-bundle-release/): There is a poll every 10 minutes for SCM changes that triggers the following activities for the 'devel' branch:
|
|
|
1. Run tests
|
|
|
2. Build the code
|
|
|
3. Generate the bundle and the update-site.
|
|
|
4. The artifacts are copied to the public repository https://download.eclipse.org/chess/core/releases/devel/.
|
|
|
- [master MAN build-bundle-release](https://ci.eclipse.org/chess/job/master%20MAN%20build-bundle-release/): This job performs the following activities for the 'master':
|
|
|
1. Run tests
|
|
|
2. Build the code
|
|
|
3. Generate the bundle and the update-site.
|
|
|
4. The artifacts are copied to the public repository https://download.eclipse.org/chess/core/releases/. Remember to change the version of the new bundle:
|
|
|
- in the org.polarsys.chess.configuration.pom.xml
|
|
|
- in the Post Steps script of this configuration (click on 'Configure', section 'Post Steps').
|
|
|
- [merge-branch-x-to-devel](https://ci.eclipse.org/chess/job/merge-branch-x-to-devel/): Activities to be triggered by the user for the branch to be merged into the devel:
|
|
|
1. In the job configuration (click on 'Configure', section 'Source Code Management/branches to build'), edit the name of the branch that must be merged into 'devel'.
|
|
|
2. Run the job (click on 'Build Now')
|
|
|
- [merge-branch-devel-to-master](https://ci.eclipse.org/chess/job/merge-branch-devel-to-master/): Activities to be triggered by the user for the branch devel to be merged into the master |
|
|
\ No newline at end of file |