commit | 95a9fe57db4ed3dc05e57786ecfbb6901bf0474d | [log] [tgz] |
---|---|---|
author | Marcus Hoepfner <marcus.hoepfner@sap.com> | Sun Nov 10 19:04:24 2019 +0100 |
committer | Matthias Becker <ma.becker@sap.com> | Tue Nov 19 04:24:35 2019 -0500 |
tree | e6b6a5ac0334fb6154039f136a028dd670ba7c99 | |
parent | 4a960d0cbc6f91ce5ac0cd6819dd1004122354b3 [diff] |
Bug 552065: add more javadoc to the abstract classes - usually uses the first sentence of the javadoc of the actual method of the widget Change-Id: I96682e5b6d8b5c38ee0d72b8e86864d188af2dea Signed-off-by: Marcus Hoepfner <marcus.hoepfner@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 library. Please install them from the Orbit Download page
Currently the following versions 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.