commit | 737cac1d546fded46f8770d311df6b6482d34693 | [log] [tgz] |
---|---|---|
author | Andrey Loskutov <loskutov@gmx.de> | Mon Mar 23 20:31:24 2020 +0100 |
committer | Andrey Loskutov <loskutov@gmx.de> | Mon Mar 23 22:11:35 2020 +0100 |
tree | 86e5312c8d6292d419ed61823e565b295a13e2b0 | |
parent | 4eb69c1e38de97b3d9f6faf62fa775a9c289c358 [diff] |
Bumped bundle version for 4.16 changes org.eclipse.e4.ui.ide change was in commit 361abe8578f5382ab7d80eec15130b0061ab4017 org.eclipse.ui.views.log change was in commit ee6c7c1064e6b64a09c9ae2139b0a813823290a3 Change-Id: I148f41022a7239d1948a01050ede60ede0eee16d Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
Thanks for your interest in this project.
Platform UI provides the basic building blocks for user interfaces built with Eclipse.
Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.
Website: http://www.eclipse.org/platform/ui/
For more information, refer to the Platform UI wiki page.
Contributions to Platform UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the Platform UI - How to contribute wiki page page on the team wiki.
Several test plug-ins have a dependency to the Mockito and Hamcrest libraries. Please install them from the Orbit Download page]3:
Currently the following plug-ins are required:
You need Maven 3.3.1 installed. After this you can run the build via the following command:
mvn clean verify -Pbuild-individual-bundles
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.