| commit | 5e31f037846f4e2ac3a166171ccabb8114e02220 | [log] [tgz] |
|---|---|---|
| author | Pauline DEVILLE <pauline.deville@cea.fr> | Thu Jan 04 17:36:30 2024 +0100 |
| committer | Pauline DEVILLE <pauline.deville@cea.fr> | Thu Jan 04 17:36:30 2024 +0100 |
| tree | 572d832811418f4c60738df5881b80545f46345a | |
| parent | 6ec37d2b340da1cbab9fb3285d17605e58cb6d5f [diff] |
Bug 581994 - [Releng] move to version 1.9.100 Change-Id: Ib3bf3de38493b0a4d3a58ebf5ea13e10d81a9a13 Signed-off-by: Pauline DEVILLE <pauline.deville@cea.fr>
Eclipse XWT is a powerful declarative UI in XML for Eclipse. It is a thin layer of markup language by unifying Eclipse SWT/JIFace and Eclipse JFace Databinding in one. It simplifies the UI development in Eclipse and open a door to provide more tools such as: Visual editing using Windows Builder Model Driven UI. Papyrus uses XWT to generate the “Properties View” for UML model editing.
These instructions will get you a copy of the project up and running on your local machine for development and/or testing purposes.
The things you need before installing the software.
In order to install the software you will have to open the downloaded IDE and install it via the integrated installer.
$ Open the Help menu of your selected IDE. $ Go to Install New Software. $ Enter the URL of the selected Papyrus update site in the 'Work with' field and select the features to install. The default one is Papyrus for UML that will give you access to the tool. $ Click on Next; the installer will automatically compute the required dependencies from the urls available. $ Accept the licences of the tools you want to install and click on finish. You will need to restart the IDE to finalize the installation.
XWT is meant to be compiled with maven. To do so you will need to fetch the git repository. It can be found [here] (https://git.eclipse.org/r/plugins/gitiles/xwt/org.eclipse.xwt/)
$ mvn clean verify
You can contribute to the Eclipse XWT project via [Gerrit] (https://git.eclipse.org/r/q/project:xwt/org.eclipse.xwt). If you are interested, you can see a detailed sequence in [this page] (https://wiki.eclipse.org/Gerrit). Contributions should be done based on the master branch in order to be automatically verified by its associated Jenkins job.