commit | a44858ef600a42cb0b8e259e77767f9a48005865 | [log] [tgz] |
---|---|---|
author | Tobias Melcher <Tobias.Melcher@sap.com> | Thu Oct 22 16:11:07 2020 +0200 |
committer | Matthias Becker <ma.becker@sap.com> | Mon Oct 26 07:47:57 2020 -0400 |
tree | c8c537dac15f8cd72ed5c1b5c2d22e15b7aed551 | |
parent | 44de0395e0857832bf36e76a4cb8ea81c81ebdd1 [diff] |
Bug 567813 - remove os_version from e4_default windows theme there is only one e4_default theme for windows and therefore no need to distinguish between different os versions Change-Id: I79275be1a48b8c83494b3ee1959d7bcd4ee4cfc6 Signed-off-by: Tobias Melcher <Tobias.Melcher@sap.com>
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.